I haven't played with Atmosphere specifically, but I've played a bit Jetty continuations, or Servlet 3's startAsync in Tapestry.
It's not a trivial integration, but I've gotten something barely working using Jetty's Continuations. For my solution I created an @AsyncEvent which essentially hijacks the event method and wraps it in a Runnable that gets dumped into a threadpool. When the method completes it resumes the continuation. The challenge is that both the Servlet3 and Jetty Continuation (and atmosphere from the look of it) expect you to return from your event method when you suspend. This means that you go all they way back up the stack to the container where it notes that you've suspended the request and then re-issues the request when you resume. For tapestry, this means that it thinks you're done with the request and starts cleaning up all the injectable services that you probably still need to finish your suspended request. I did this all about 6 months ago and haven't had a chance to get into the tapestry source to work out a way to teach it about suspended requests. Josh On Tue, Apr 12, 2011 at 4:48 AM, <tmar...@gmx.de> wrote: > Hello again! > > Is there any way to get the @Broadcast annotation from Atmosphere: > > http://atmosphere.java.net/nonav/apidocs/org/atmosphere/annotation/Broadcast.html > > working inside of a Tapestry5 page or component? > > Or are there any general, architectural restrictions why this can not work in > Tapestry right now? > > If not, what changes would be necessary in order to be able to be able to use > it? > > Thanks! > > Tobias > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
