From sgcWebSockets 4.2.6 SChannel is supported in WebSocket client component

WebSocket client component can connect to secure servers using openSSL libraries, from sgcWebSockets 4.2.6 version, now can connect to secure websocket servers using Microsoft SChannel, so there is no need to deploy openssl libraries if this method is selected. To enable SChannel use TLSOptions.IOHandler property

  Client.TLSOptions.IOHandler := iohSChannel;

By default, Client uses openSSL as default method.

SChannel is only supported by Windows platform.

Changes included

 [+] : WebSocket client supports SChannel for Windows.

 [+] : New Property CertStoreName in TsgcWebsocketServer_HTTPAPI, allows to set the name of certificate store where is certificate.

 [+] : New properties in SSLOptions in TsgcWebSocketServer, allows to set TLS Version and VerifyCertificate.

 [+] : MQTT Client now accepts Client Identifiers with more than 23 characters.

 [+] : Update Client Demo to show how connect to AWS AppSync.

 [+] : New Property UserAgent in SocketIO API.

 [*] : Improved speed TsgcWebsocketServer_HTTPAPI, when connection doesn't requiere authorization.

 [*] : Fixed Bug Server SGC Protocol, error reading broker message, when TsgcWebSocketServer_HTTPAPI is attached.

 [*] : Fixed Bug Server File Protocol, error reading broker message, when TsgcWebSocketServer_HTTPAPI is attached.

 [*] : Fixed Bug Server Presence Protocol, error reading broker message, when TsgcWebSocketServer_HTTPAPI is attached.

 [*] : Fixed Memory Leak Presence Protocol (Server and Client), TsgcWSAckMessages were created and not destroyed.

 [*] : Fixed Bug compiling Lazarus for Linux, sgcWebSockets_Resources file is not found.

 [*] : Fixed Bug compiling Lazarus for Linux, sgcResources.res file is not found.

 [*] : Fixed Bug compiling Lazarus for Linux, Abstract methods cannot be called directly in sgcWebSocket_Server_Base.LockList method

 [*] : Fixed Bug connecting to a server behind CloudFlare proxy.