title: Websockets with ASP.NET MVC / MVVM
body: <p>Earlier today I came across <a href="http://kaazing.com" rel="noreferrer">Kaazing's</a> WebSocket API for HTML5.</p>
  
  <p>Looks fantastic, but as I am only now researching WebSocket possibilities for real-time financial updating, I would like to hear some recommendations, and pitfalls to avoid when planning out this architecture.</p>
  
  <p>I'm looking at ASP.Net MVC, and possibly some WPF/Silverlight MVVM.</p>
  
  <p>Are there other WebSocket API's that are better (and why), and some good examples?</p>
  
  <p>Also, what kind of traffic can WebSockets handle?  I mean, if we have over a million users on a system updating real-time, how do hardware requirements change because the software architecture implements WebSockets?</p>