title: Limiting performance factors of WebSocket in ASP.NET 4.5?
body: <p>MSDN documentation doesn't seem to have good coverage on ASP.net 4.5 support of HTML5 <a href="http://msdn.microsoft.com/en-us/library/system.web.websockets.aspnetwebsocket.aspx">WebSockets protocol</a>!</p>
  
  <p>This is what I'm looking for:</p>
  
  <ul>
  <li>How many live connections can a server/application/cpu support? </li>
  <li>Is there any maximum number of incoming connections that could be set/get?</li>
  <li>What is the optimum number of sockets per application regardless of data transfer over the socket?</li>
  </ul>
  
  <p><strong>Update:</strong></p>
  
  <p>Requests from flash RTMP sockets (an alternative to websocket) could be well configured on <a href="http://help.adobe.com/en_US/flashmediaserver/configadmin/WS5b3ccc516d4fbf351e63e3d119f2925e64-7ff0.html">Adobe Media Server</a> application server. Isn't any sort of configurations for number of requests, ideal time, size of chunks, ... for ASP.net inside application or IIS 8 configuration?</p>