[Dojo-interest] Re: Comet

Kyle Himmerick himmeric at vnet.ibm.com
Fri Apr 14 06:16:12 MDT 2006


I'd like to get in sync with this generic format as it develops.  I'd 
also like to see a Comet pub/sub implementation in ActiveMQ (JMS) with 
Jetty Continuations.

Greg, it looks like you've contributed to the ActiveMQ project with 
their AJAX interface.  I'm thinking there will be minor changes here to 
sync up with a generic format and to keep the connection open until a 
timeout occurs.

Alex can you give us a general idea where you think you'd like to go 
with this?  I saw some of your notes on data grams, were you thinking 
XML/JSON?  REST API's I'm assuming for publishing and 
subscribing/unsubscribing.  Are you thinking IFrameTransport for chunked 
responses/subdomain support or polling xmlhttprequest for complete 
datagrams.

Can we start hashing out some of the details with all the interested 
parties here on the mailing list?

Best Regards,
Kyle Himmerick
himmeric at vnet.ibm.com

Alex Russell wrote:
> Hi Greg!
>
> On Thursday 30 March 2006 5:58 am, Greg Wilkins wrote:
>   
>> Alex Russell wrote:
>>     
>>> On Sunday 26 March 2006 11:40 pm, Rafael Maga?a wrote:
>>>       
>>>> How can I implement Comet with dojo.io.bind()?
>>>>         
>>> Right now it requires a custom server and transport to plug into
>>> dojo.io.bind()'s plugin mechanism. We're still working on a freely
>>> available client/server pair. Sorry for the wait.
>>>       
>> Alex,
>>
>> I'd be really keen to add a component to Jetty 6 to support the
>> server-side of such a pairing.
>>     
>
> Interesting. I'd love to see that as well. Right now I'm working on what 
> will (hopefully) be a portable client for soemthing like this. There's 
> a Perl-centric implementation happening under the name of "ShortBus" 
> and I'm working on a stand-alone Twisted variant. Once we've got those 
> mostly functional, I think we should publish the JSON format and HTTP 
> endpoint verbs which would let you easily implement it.
>
> If you'd like to be involved sooner while we're figuring out some of the 
> path router semantics, let me know.
>
> Regards
>
>   
>> Jetty 6 continuations are exactly what you need for efficient
>> long-polling in the java space.  The mechanism is also portable
>> to other servers (but is just a wait and does not free the
>> thread or other resources) - but I need to do a portable assembly.
>>
>> If you can expand on your plans for long polling with bind, then
>> I'm happy to write the server side to match.
>>
>> cheers
>>     
>
>   



More information about the Dojo-interest mailing list