title: SPA: using websockets only. Why not?
body: <p>I am redesigning a web application which previously has been rendered server side to a Single Page Application and started to read about websockets . The web application will be using sockets to have new records and/or messages pushed to the client. I have been wondering why most pages which make use of sockets don't handle all their communication over the socket. Most of the times there is RESTful backend in addition to the websocket. Would it be a bad idea to have the client query for new resources over the socket? If so why - other than that a RESTful api might be easier to use with other devices?</p>
  
  <p>I can imagine that using websockets would probably not be the best idea in case the network connection is kind of bad like on mobile devices, but that probably should work quite well with a reasonable connection to the web.</p>
  
  <p>I found this related question, however it is from 2011 and seems a little outdated:
  <a href="https://stackoverflow.com/questions/6806263/websocket-api-to-replace-rest-api">websocket api to replace rest api?</a></p>