I recommend Nginx + Jetty. Apache is the worst front end for this situation... it can only support a few hundred simultaneous connections before it falls over. Ngnix on the other hand can proxy tens of thousands.
Jetty's continuations make it a much better choice than Tomcat. You can have thousands of open Comet request to a Jetty instance where Tomcat is capped at a couple of hundred. Once the Servlet 3.0 spec in implemented in Glassfish, etc., Lift will support 3.0 continuations and any 3.0 container will have the same scaling characteristics that Jetty currently does. On Thu, Nov 19, 2009 at 5:35 PM, Neil.Lv <[email protected]> wrote: > Hi all, > > I have a silly question about the deploy. > > Which web container is recommended to use to deploy the Lift app ? > Jetty or Tomcat ? > > I want to use the Comet to push the data in the app. > > * Apache + Tomcat ? > * Apache + what ? > * Nginx + what ? > > Thanks for any suggestion ! > > Cheers, > Neil > > -- > > You received this message because you are subscribed to the Google Groups > "Lift" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<liftweb%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/liftweb?hl=. > > > -- Lift, the simply functional web framework http://liftweb.net Beginning Scala http://www.apress.com/book/view/1430219890 Follow me: http://twitter.com/dpp Surf the harmonics -- You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/liftweb?hl=.
