sgcWebSockets 4.1.11

With sgcWebSockets 4.1.11 we improve Microsoft HTTP API Server and improve performance and stability

 

 Full List of Changes:

 

[+] : MQTT Protocol now support publishing binary data.

[+] : New demo called "Mobile" replace "iOS" demo and shows how connect to a secure WebSocket server in Android 7.0+.

[+] : New Property in HTTP API Server, Timeouts, allows to override default timeouts of HTTP API Server.

[+] : New Property in HTTP API Server, ThreadPoolSize, by default 32 (maximum allowed is 64), allows to set number of threads of HTTP API Server.

[+] : New Property in HTTP API Server, MaxBandwidth, maximum allowed bandwidth rate in bytes per second (zero means unlimited, value by default).

[+] : New Property in HTTP API Server, MaxConnections, maximum number of connections (zero means unlimited, value by default).

 

[*] : Fixed Bug AppRTC Protocol, when close call and try to rejoin shows an error.

[*] : Fixed Memory Leak in MQTT Protocol component when destroying object.

[*] : Fixed Bug MQTT Protocol, Packet Identifier was not read properly and if QoS = "At least once" or "Exactly once" messages could be sent duplicated.

[*] : Fixed Bug MQTT client, after reconnect queued messages where not published.

[*] : Fixed Memory Leak in STOMP Protocol component when destroying object.

[*] : Fixed Error compiling in Lazarus for Linux with unit sgcWebSocket_Resources, unit name was incorrect.

[*] : Fixed Bug HTTP API Server, when adding new binding with a parameter, this was not read properly in some cases.

[*] : Fixed Bug HTTP API Server, size of payload message was not calculated properly.

[*] : Fixed Bug HTTP API Server, only one thread was created to handle client connections.

[*] : Fixed Bug HTTP API Server, disconnect event was not called in some cases.

[*] : Fixed Memory Leak in HTTP API Server, internal heartbeat timers were not destroyed.

[*] : Fixed some minor Bugs HTTP API Server.

[*] : Fixed Bug in QueueLevel properties, if there is a disconnection before all queues are processed a memory leak can occur.

[*] : Fixed Bug using Queues, in some cases stream was not saved properly.

[*] : Fixed Bug LoadBalancer calculating server client connections count.

[*] : Fixed Bug error "invalid pointer", notifying subscription/unsubscription when notifyEvents = neAsynchronous.