github.com/drawdy/stomp-ws-go (go): Package stompngo implements a STOMP 1.1+ compatible client library. For more STOMP information, see the specification at: http://stomp.github.com/.  Network Connect:  You are responsible for first establishing a network connection.  This network connection will be used when you create a stompngo.Connection to interact with the STOMP broker.  Network Disconnect:  When processing is complete, you MUST close the network connection.  If you fail to do this, you will leak goroutines!  The STOMP specification defines these physical frames that can be sent from a client to a STOMP broker:  The STOMP specification defines these physical frames that a client can receive from a STOMP broker:  The Subscribe method returns a channel from which you receive MessageData values.  The channel returned has different characteristics depending on the Stomp Version, and the Headers you pass to Subscribe.  For details on Subscribe requirements and behavior, see: https://github.com/gmallard/stompngo/wiki/subscribe-and-messagedata  Receipts are never received on a subscription unique MessageData channel.  They are always queued to the shared connection level stompgo.Connection.MessageData channel.  The reason for this behavior is because RECEIPT frames do not contain a subscription Header (per the STOMP specifications).  See the:  https://github.com/gmallard/stompngo_examples  package for several examples.
Keywords: golang|stomp|stompwebsocket