title: Web sockets server side processing model
body: <p>To implement a server supporting clients using <a href="http://en.wikipedia.org/wiki/Web_socket" rel="noreferrer">web sockets</a>, do servers keep an open HTTP connection with each client?  How can this scale?</p>
  
  <p>What are the "programming models" when implementing this type of server?  Ie: most web apps have servlets, etc which support a connect->request->response->close type model.  Whereas with web sockets the connect stays open indefinitely. </p>