Hi Jaime,

Thanks, I've added the link as a new comment. Feel free to comment
issues/RFEs directly if you want to.

Best regards,
Jerome  

> -----Message d'origine-----
> De : jbarciela jbarciela [mailto:[EMAIL PROTECTED] 
> Envoyé : mercredi 6 février 2008 21:34
> À : [email protected]
> Objet : Re: Evaluating Restlet
> 
> a possible addition to that list (probably you know the link but I
> didn't see it in the list), is Tomcat 6's approach, they named the
> interface "CometProcessor"
> 
> http://tomcat.apache.org/tomcat-6.0-doc/aio.html
> 
> hope it helps
> Jaime
> 
> 
> On Feb 5, 2008 6:01 PM, Rob Heittman 
> <[EMAIL PROTECTED]> wrote:
> >
> > Exactly ...
> >
> > In my case, I'm working on Restlet API support in Google 
> Web Toolkit using
> > XmlHttpRequest as the "Client".  As this is idiomatically 
> an asynchronous
> > facility -- regardless of whether your response is short 
> lived (AJAX style)
> > or long lived (Comet style), the API needs ways of handling 
> clients that
> > behave asynchronously, which it presently lacks.  Several 
> interesting
> > connectors like Jetty have also introduced neat new 
> facilities driven by the
> > desire to make the Comet style more manageable on the 
> server side, so it's
> > not just about the client side.
> >
> > Have a look at this RFE and its references:
> > http://restlet.tigris.org/issues/show_bug.cgi?id=143   ...  
>  you guessed
> > right, it started with an observation about the Comet style.
> >
> > - Rob
> >
> >
> >
> > On 2/5/08, jbarciela jbarciela <[EMAIL PROTECTED]> wrote:
> > > When you say "callbacks", what do you have in mind? 
> Something like Comet?
> > >
> > > Cheers
> > > Jaime
> > >
> >
> >

Reply via email to