Maybe it isn't different. I'm not an expert on the HTTP transport. In general, a keep-alive is transparent to the Synapse message flow - it is effectively managed by the client and each request-response pair is logically separate. A comet connection logically supports both in and out messages in any order and something needs to indicate to the transport which existing connection this message is going to. For example, suppose you have 50 incoming connections, each of which is looking for different stock quotes based on a filter, something needs to decide which connections to send the MSFT quote down when it comes in. I guess logically speaking, we need a unique to-address for each open connection so that it can be addressed by a message.
Paul On Mon, Jul 21, 2008 at 1:24 PM, Sanjiva Weerawarana <[EMAIL PROTECTED]> wrote: > 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] > > -- Paul Fremantle Co-Founder and CTO, WSO2 Apache Synapse PMC Chair OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [EMAIL PROTECTED] "Oxygenating the Web Service Platform", www.wso2.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
