title: ssl handshake again for wss after initial for https?
body: <p>Assume a 100% secure websocket site where the webserver serves all files: html, js, css, etc, and the websocket serves all data between client and server.</p>
  
  <p>Obviously the initial ssl handshake is between the client and webserver on the default https port, but wss will be on a different port, so does it have to handshake again?</p>
  
  <p>The reason I'm asking is because websockets &amp; spdy aren't working together yet (so I've read), so I'm hoping to get around it by having spdy on the webserver and rely on keep-alive for wss since some claim spdy isn't much faster (if at all) than keep-alive after the handshake <a href="https://stackoverflow.com/questions/15255039/spdy-faster-than-keep-alive-https">spdy faster than keep-alive https?</a>.</p>