YoJimbo
unread,Jan 4, 2011, 1:51:11 PM1/4/11Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Lift
Hi
I have read previous mailing list submissions, and understand that
lift will work across jetty, tomcat, glassfish, jboss, resin etc.
And that any servlet container that fully supports the servlet 3.0
spec will be able to take advantage of continuations to prevent
connected but idle requests from eating server resources.
That said -
* If I downloaded, extracted and fired up the latest nightly build of
glassfish v3 - would I need to make any specific changes to my lift
app or the server to take advantage of continuations? Or will it
automagically work?
* Glassfish in particular seems to be gaining alot of momentum. For
customer product demonstrations, the clustering capabilities and
commercial support from Oracle are nice. I know that jetty is the
default go to app server for the lift community. I suspect this is due
to historically it being the absolute best choice for out the box NIO
support. Is it still realistically a must to use Jetty in production
environments? Though the other options work, would/do people consider
using other products in production?
* Lastly before we conduct our own benchmarks - has anyone run any
recent comet focused load-testing on Jetty vs other app servers
running lift apps?
Regards,
JP