title: Support SSL and non-SSL on the same port
body: <p>I'm working on adding SSL support into our existing application and have started to think about backwards compatibility.</p>
  
  <p>The one special case that makes this different than other posts I've read is the server may not necessarily be updated with SSL code.  So I'll have an SSL client connecting to a server that knows nothing about SSL.</p>
  
  <p>For the sake of this discussion, the application sends keystrokes one at a time to the server, and for each keystroke a new socket is created.  So I need to figure out a way to make this work on the existing port number and not use timeouts to determine if the server supports SSL or not.</p>
  
  <p>Any suggestions on a graceful way to handle this?</p>
  
  <p>(I'm using Winsock and OpenSSL)</p>