title: HTML5 Server-Side Event: EventSource vs. wrapped WebSocket
body: <p>Is the HTML5 Server-Sent Events (SSE) API just a restricted, event-based API on top of HTML5 WebSockets?</p>
  
  <p>It seems to me that an <code>EventSource</code> is just a <code>WebSocket</code> that:</p>
  
  <ol>
  <li>Cannot <code>.send()</code> data</li>
  <li>Uses the <code>text/event-stream</code> format</li>
  <li>Fires dynamically-named (server-defined) events instead of <code>onmessage</code></li>
  </ol>
  
  <p>The idea of the web server pushing events down to client devices is quite intriguing. Does this API have any traction?</p>
  
  <p>I imagine the async event model would work beautiful when couple with Node, but not seeing a lot of use cases for this in my ASP.NET world.</p>