title: STOMP vs WAMP over Spring-WebSockets
body: <p>I am currently working on a project that needs to work with WebSockets.
  The clients will be the browsers only, so not interested in any message broker feature of these two.</p>
  
  <p>Although I don't think that it would be much a difference, but would be interested if I can get a few comments on <a href="http://stomp.github.io/">STOMP</a> vs <a href="http://wamp.ws/">WAMP</a> as a subprotocol using Spring-WebSockets. </p>
  
  <p>And I might get a few hints that may help choose one over the other.</p>
  
  <p>Cheers,</p>
  
  <p><strong>EDITED (27-02-2014):</strong>
  As, programming directly with webSockets is low-level, so its suggested in many places (one the spring documentation) to use some sub-protocol.</p>
  
  <p>Also, the use of a sub-protocol over websocket, is a type of native webSocket security; like you can do a sub-protocol validation.</p>
  
  <p>There are many other sub-protocol that can be used instead of STOMP or WAMP like XMPP, AMQP.
  I couldn't find much information related to these and webSockets, most of it is related to message brokers only.</p>