Hey Marius, Im not 100% sure that Servlet 3.0 will solve our problems... im worried that the vendors will not standardise once again (they are already diverging paths in "early access" servlet 3.0 implementations)...
To this end, I cant help but wonder if we will end up falling back on something like Atmosphere to become container agnostic? Cheers, Tim PS: Sorry for the semi thread-hijacking! On Dec 2, 8:15 pm, Marius <marius.dan...@gmail.com> wrote: > Lift doesn't necessarily require Jetty 6. Lift runs pretty much on any > JEE web container including jetty 7. But Lift comet support > automatically detects Jetty 6 continuations API and use it. If that is > missing Lift will gracefully fall back in using a locking based > mechanism for Comet. Of course this model does not scale very well. > > The reason for that Jetty 7 continuations API is not in Lift yet is > because we were waiting for Servlet 3.0 Async support (similar in many > respects with Jetty 7 continuations). But servlet 3.0 is not there > yet ... still Jetty 7 contains some more or less experimental > implementation of Servlet 3.0 Async. I'm using at work jetty 7 > continuations which is quite a nice API ... even nicer that servlet > 3.0 spec :D > > Br's, > Marius > > On Dec 2, 9:30 pm, jhonig <al...@xs4all.nl> wrote: > > > > > Hi Tim, > > > > Lift is not yet compatible with Jetty 7 continuations... if you want to > > > use comet, please use Jetty 6 for the moment. > > > I don't use comet. But is this dependency mentioned anywhere in the > > Lift docs? Can't remember > > having seen any such information! > > > Job -- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to lift...@googlegroups.com. To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/liftweb?hl=en.
