title: What are the advantages of websocket APIs to middleware?
body: <p>Some pieces of middleware support websockets natively e.g. HiveMQ: <a href="http://www.hivemq.com/mqtt-over-websockets-with-hivemq/" rel="nofollow">http://www.hivemq.com/mqtt-over-websockets-with-hivemq/</a>. What advantages are conferred to a developer using the websockets API as a first class client to the middleware, rather than routing requests through an intermediary server that supports language specific APIs e.g.</p>
  
  <p>Client -> Middleware</p>
  
  <p>vs</p>
  
  <p>Client -> Server -> Middleware</p>
  
  <p>For example, we could argue that skipping an intermediary server will reduce bandwidth costs, not require a developer to write an extra layer, native SSL websockets support? </p>
  
  <p>What other advantages might be provided to not just a developer, but any party through providing websockets support for middleware?</p>