search

rabbitmq / rabbitmq-web-stomp

Provides support for STOMP over WebSockets
Other
89 stars 26 forks source link

Improvement: document /stomp/websocket endpoint #26

Closed spatula75 closed 9 years ago

spatula75 commented 9 years ago

At https://www.rabbitmq.com/web-stomp.html#usage , the documentation correctly indicates that a SocksJS STOMP endpoint is exposed at /stomp .

It would be an excellent improvement in documentation to indicate that in addition to this endpoint, STOMP over WebSocket is exposed at /stomp/websocket for WebSocket STOMP clients other than SocksJS.

essen commented 9 years ago

In 3.6.0, we are adding an endpoint at /ws that not only is just STOMP over WebSocket, but also allows you to use binary frames rather than UTF-8 text frames as it is currently impossible to transmit binary data.

You can already try it by using the current master of this plugin. Feedback welcome!

spatula75 commented 9 years ago

I'll try to have a look soon. We will likely postpone the feature for which we are using the plugin until 3.6 anyway because of other issues that are apparently also fixed in 3.6.

Binary won't affect use since our objects are all serialized as JSON.

Will give it a shot and see how it works for us anyway. On Sep 18, 2015 2:44 PM, "Loïc Hoguin" notifications@github.com wrote:

In 3.6.0, we are adding an endpoint at /ws (IIRC) that not only is just STOMP over WebSocket, but also allows you to use binary frames rather than UTF-8 text frames as it is currently impossible to transmit binary data.

You can already try it by using the current master of this plugin. Feedback welcome!

— Reply to this email directly or view it on GitHub https://github.com/rabbitmq/rabbitmq-web-stomp/issues/26#issuecomment-141576080 .

michaelklishin commented 9 years ago

The /ws endpoint has been documented in master.