java - STOMP vs WAMP over Spring-WebSockets -
I am currently working on a project that needs to work with websacetes. The client will be the only browser, so neither of these two messages are interested in the broker facility.
Although I do not think that this will be a lot different, but I would be interested if I used to comment on some versus vs. subprotocol using spring-websacents.
Cheers,
Edited (27-02-2014)
: As such, programming directly with webcapsets is low-level, so it is possible to use several sub-protocols In many places (a spring document) is recommended for.
In addition, the protocol on the sub-website is a type of country web site security; Just like you can do a sub-protocol verification.
There are many other sub-protocols that can be used instead of STOMP or WAMP instead of XMPP, AMQP. I can not find more information related to these and websacet, most of them are related to message brokers only.
One reason (obvious) that I should use STOMP on any other sub-protocol I'm using Spring-Websococents, so for STOMP I do not need to add any extra library to the server, others will need me to serve me. There are several JS libraries in the client, which I can use for similar types of JS for socket.io and WAMP for STOMP and others.
Since, my main concern is to the server: Therefore, STOMP is
If I find out something new when implementing my solution, then I will update this post.
Comments
Post a Comment