Hello,

Thanks for the great networking library. Its made my life countless time
easier.

I'm the lead developer of the Orbited project (www.orbited.org) which is a
python server built using pyevent (libevent wrapper for python) that
maintains many long-standing HTTP connections for the purpose of HTTP push
(Also known as Comet, see: http://en.wikipedia.org/wiki/Comet_(programming).
There is a fair amount of python code in Orbited devoted to implementing an
HTTP server and proxy. For speed, memory usage, and maintainability, It
would make a lot more sense to simply use the libevent http server/client,
if its a good idea.

In order to implement an HTTP push client in browsers though, all sorts of
tricks are necessary. There are two hard requirements for the server:

- Keep-alive support. HTTP push applications must have a keep-alive support
to reduce latency in responding to the server
- Incremental response - Orbited needs to be able to send some headers right
away, then later send part of the body, then later send some more. For
instance, one method of doing http push is to send "<script>callback('some
data');</script>" every time some new data becomes available. The connection
might be open for 5 hours with bits and pieces coming in every few minutes.

I couldn't tell from the docs whether these two items are possible with the
libevent http server.

Thanks,

Michael Carter
_______________________________________________
Libevent-users mailing list
Libevent-users@monkey.org
http://monkeymail.org/mailman/listinfo/libevent-users

Reply via email to