That's good to know. But now that Tim has made me aware of the possibilities of Jetty, I might be persuaded to stick with it. Need to figure out how to host multiple sites in one instance, and discover where this context deployer is hidden.
If I can get that running, I write a brief tutorial for the website. (Don't hold your breath... I'm buried with work and not very bright.) Chas. David Pollak wrote: > > > On Mon, Mar 16, 2009 at 6:39 AM, Timothy Perrett > <[email protected]> wrote: > > > > Im hosting several sites on a single jetty install - its working > perfectly > right now. Are you not familiar with the virtual hosting options in > jetty? > Its pretty well documented on their wiki and will let you host from > the root > context. > > Someone can correct me if im wrong, but until servlet 3.0 spec comes > out, I > believe were only supporting comet in Jetty. So if your planning a > move to > Glassfish, you'll loose the comet support. > > > This is absolutely wrong. Lift supports Comet *NO MATTER WHAT CONTAINER > YOU USE*!!! (Sorry for jumping up and down on this, but it's very > important that people not think that Lift's features are container > dependent.) > > Lift takes advantage of Jetty continuations to reduce resource > consumption on the server by not consuming a thread during long polling. > This means that if you have more than 500 simultaneous connections to a > server, it'll consume a ton of resources on Tomcat and very few on Jetty. > > > > > Can you not use the context deployer in jetty to do what you need? > > Thanks > > Tim > > > On 16/03/2009 13:07, "Charles F. Munat" <[email protected] > <mailto:[email protected]>> wrote: > > > Right now I'm running about a half dozen instances of Jetty (one per > > site). I'm starting them with java -jar ..., and stopping them > with kill > > -9, which I think is a total hack. To find out what's running, I > do a ps > > aux | grep jetty. Seriously? In 2009? > > > > With Glassfish (or Geronimo or equivalent), I get a nice > interface and I > > can deploy pretty easily. I can see exactly what's going on. I > can start > > and stop servlets easily, and I can set things up to restart > > automatically on server reboot (instead of writing a shell script). > > > > And I'm hoping that despite the higher overhead of Glassfish, > that when > > I get enough sites in there it will be lower than running that many > > separate instances of Jetty. > > > > There may be other things I'd like to play with as well (access > control, > > etc.). > > > > The thing that holds me back is that when I deploy multiple sites to > > Glassfish, a site like mysite.com <http://mysite.com> is actually > deployed to > > mysite.com/mysite <http://mysite.com/mysite>. That extra context > in the path is a showstopper. But > > I have been unable to figure out how to get rid of it. > > > > I'm open to other suggestions, but there has to be some way for me to > > host multiple sites with some sort of interface and an easy way to > > deploy, restart, monitor, etc. them. > > > > Chas. > > > > Timothy Perrett wrote: > >> > >> Phew :) > >> > >> Out of interest, why do you want to use glashfish rather than jetty? > >> > >> Tim > >> > >> On 16/03/2009 10:08, "Charles F. Munat" <[email protected] > <mailto:[email protected]>> wrote: > >> > >>> Just Jetty on the server. Maven/Jetty while developing. (I'm > not that > >>> dumb.) :-) > >>> > >>> Chas. > >> > >> > >> > >>> > > > > > > > > > > > > > > > -- > Lift, the simply functional web framework http://liftweb.net > Beginning Scala http://www.apress.com/book/view/1430219890 > Follow me: http://twitter.com/dpp > Git some: http://github.com/dpp > > > --~--~---------~--~----~------------~-------~--~----~ 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=en -~----------~----~----~----~------~----~------~--~---
