Hi there,<div><br></div><div>I&#39;ve been experimenting a bit with the new EventSource API (<a href="http://hacks.mozilla.org/2011/06/a-wall-powered-by-eventsource-and-server-sent-events/">http://hacks.mozilla.org/2011/06/a-wall-powered-by-eventsource-and-server-sent-events/</a>).</div>
<div><br></div><div>EventSource looks like a much nicer alternative to WebSockets in all the cases where the connection doesn&#39;t really need to be bi-directional (ajax request to push to the server, Event Source to push to the client). It doesn&#39;t require a new protocol and should be trivial to pass through HTTP aware load balancers, cache proxies and so on.</div>
<div><br></div><div>Have been trying to get either Snap or Warp to serve up an EventSource endpoint, but so far I&#39;m stuck at not being able to get any of them to actually write to the response body before the request is all over.</div>
<div><br></div><div>Here&#39;s some example code:</div><div><br></div><div>Snap based: <a href="https://gist.github.com/1174102">https://gist.github.com/1174102</a></div><div>WAI/Warp based: <a href="https://gist.github.com/1174632">https://gist.github.com/1174632</a></div>
<div><br></div><div>The code is mostly the same apart from the glue to the web server. In both cases I&#39;m trying a silly enumerator that gets messages from the keyboard and pass them to the iterator.</div><div><br></div>
<div>It all compiles and kinda works, but nothing gets written to the response before I end the enumeration with &quot;q&quot;.</div><div><br></div><div>Any hints on what I&#39;m doing wrong? Or any example code for controlling writes to the response body during a long request?</div>
<div><br></div><div>Cheers,</div><div>Mathias</div>