hi5 is running tomcat 6.0 for our Shindig instance. Works quite well if tuned appropriately. I'll be talking a bit about our experience deploying our implementation at Google IO next week.
On 5/19/08 4:38 PM, "Kevin Brown" <[EMAIL PROTECTED]> wrote: > On Mon, May 19, 2008 at 4:16 PM, Alejandro Rivero <[EMAIL PROTECTED]> > wrote: > >> continuing wuth the requests of help for java-novices... Ok, we are >> pretty happy with shindig and plan to jump to production in a couple >> weeks. Should we keep the same deply, with maven and jetty? Should we >> get some gain not using maven to launch? Or should we get the .war or >> .jar or .whatever and deploy it in Tomcat? > > > I've seen a few production sites using jetty, but not many. I've personally > never used jetty in a production setup so I don't know what people might > actually like. Christian did some experiments to try deploying shindig to > different containers and he found some minor issues with tomcat (mostly > config changes), but otherwise it's pretty good. > > I believe Paul mentioned that he uses Tomcat (or some modified version > thereof) at hi5. We use a proprietary solution at Google. I'm not sure what > else is in use. > > >> >> If the later, then a rough description of the procedures could be >> helpful. Thanks, >> >> Alejandro >>
