sgcWebSockets 4.1.6

With sgcWebSockets 4.1.6 we introduce new STOMP Protocol. STOMP provides an interoperable wire format so that STOMP clients can communicate with any STOMP message broker to provide easy and widespread messaging interoperability among many languages, platforms and brokers. There are 3 new protocol clients:

1. Generic STOMP Protocol client: allows to connect to virtually any STOMP Server.

2. RabbitMQ STOMP client: client for RabbitMQ Broker, using STOMP.

3. ActiveMQ STOMP client: client for ActiveMQ Broker, using STOMP.

 

WebSocket STOMP Protocol

Download WebSocket Client DEMO 

 

SGC WebSocket Protocol now supports wildcards in subscribe and publish methods,  Subscription Wildcards

 

Full List of changes:

 

 [+] : New Component TsgcWSPClient_STOMP, generic STOMP Protocol client, allows to connect to any STOMP Server

 [+] : New Component TsgcWSPClient_STOMP_RabbitMQ, STOMP client for RabbitMQ Broker.

 [+] : New Component TsgcWSPClient_STOMP_ActiveMQ, STOMP client for ActiveMQ Broker.

 [+] : New Demo "Client" which shows how connect to: WebSocket Server, MQTT Server and STOMP Server.

 [+] : SGC Protocol Server, Publish method now is overloaded, new method now accepts QueueLevel (store last message or store all messages).

 [+] : SGC Protocol Server, Subscribe/UnSubscribe methods now supports wildcard characters, so you can subscribe to a hierarchy of channels. Example: if you want subscribe to all channels which start with 'news', then call Subscribe('news*').

 [+] : SGC Protocol Server, Publish method now supports wildcard characters, so you can publish to a hierarchy of channels. Example: if you want send a message to all subscribers to channels which start with 'news', then call Publish('news*').

 

 [*] : Fixed Bug Broker component processing messages when more than one protocol is attached.

 [*] : Fixed Bug BCBuilder compiling error in sgcWebSocket_WinAPI.

 [*] : Fixed Bug MQTT Client reading remaining length.

 [*] : Fixed Bug MQTT Client Heartbeat doesn't start after a disconnection.

 [*] : Fixed Bug Client when disconnecting from a thread.

 [*] : Fixed Bug TsgcPing in client component was not destroyed properly.

 [*] : Fixed Bug SGC Protocol method UnSubscribeAll was not destroying all subscriptions.

 [*] : Fixed Bug SGC Protocol if a message was published with queueLevel1, message was not retained in server.

 

 [/] : Property rename in TsgcWebSocketServer, Connections[Guid] now is ConnectionsByGuid[Guid]