You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shindig.apache.org by Alejandro Rivero <al...@gmail.com> on 2008/05/20 01:16:33 UTC
jetty in production? Which else?
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?
If the later, then a rough description of the procedures could be
helpful. Thanks,
Alejandro
Re: jetty in production? Which else?
Posted by "Henning P. Schmiedehausen" <hp...@intermeta.de>.
"Kevin Brown" <et...@google.com> writes:
>> 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.
The platform that I work on is running exclusively on Jetty, but we
use it "inside out" (no servlets). Which makes Shindig integration
"interesting". Expect a number of patche proposals coming up soon that
rip the Servlets apart.
Best regards
Henning
--
Henning P. Schmiedehausen -- hps@intermeta.de | J2EE, Linux,
91054 Buckenhof, Germany -- +49 9131 506540 | Apache person
Open Source Consulting, Development, Design | Velocity - Turbine guy
INTERMETA - Gesellschaft fuer Mehrwertdienste mbH - RG Fuerth, HRB 7350
Sitz der Gesellschaft: Buckenhof. Geschaeftsfuehrer: Henning Schmiedehausen
"...it's good to be a lunatic..." -- 10th doctor
Re: jetty in production? Which else?
Posted by Alejandro Rivero <al...@gmail.com>.
I will expect to see the video then!
2008/5/20 Paul Lindner <pl...@hi5.com>:
> 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.
>
>
Re: jetty in production? Which else?
Posted by Paul Lindner <pl...@hi5.com>.
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" <et...@google.com> wrote:
> On Mon, May 19, 2008 at 4:16 PM, Alejandro Rivero <al...@gmail.com>
> 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
>>
Re: jetty in production? Which else?
Posted by Kevin Brown <et...@google.com>.
On Mon, May 19, 2008 at 4:16 PM, Alejandro Rivero <al...@gmail.com>
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
>