On the server-side, why is Comet different from a keep-alive connection
where we have to process multiple independent requests on the same socket
connection?
Sanjiva.
Paul Fremantle wrote:
Folks
One of the things I am increasingly interested in is events and EDA,
and while Synapse already supports Atom, JMS, XMPP (tho not XMPP
pub/sub AFAIK), I think it might be interesting to think how you would
implement a Comet model
http://en.wikipedia.org/wiki/Comet_(programming) with Synapse.
It seems to me that our NIO HTTP model is very suited in one way
(async), but I guess we'd probably need to do a lot of work to support
handling more than one message per connection because its not clear to
me how you would associate the messages with the connection.
Thoughts?
Paul
--
Sanjiva Weerawarana, Ph.D.
Founder & Director; Lanka Software Foundation; http://www.opensource.lk/
Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
Member; Apache Software Foundation; http://www.apache.org/
Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/
Blog: http://sanjiva.weerawarana.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
