Re: Mod_Jk2 - Default Worker

2004-02-13 Thread Henri Gomez
Bill Barker wrote: - Original Message - From: "Costin Manolache" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, February 12, 2004 11:03 AM Subject: Re: Mod_Jk2 - Default Worker Henri Gomez wrote: Well, if we didn't get the POST somewhere o

Re: Mod_Jk2 - Default Worker

2004-02-13 Thread Henri Gomez
Costin Manolache wrote: Henri Gomez wrote: Well, if we didn't get the POST somewhere on the WebServer, and if the tomcat failed to respond, we couldn't resent the whole POST to the second one. If we get the first bytes ( but not the entire POST ), we can still save them, and if the first tomc

Re: Mod_Jk2 - Default Worker

2004-02-12 Thread Bill Barker
- Original Message - From: "Costin Manolache" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, February 12, 2004 11:03 AM Subject: Re: Mod_Jk2 - Default Worker > Henri Gomez wrote: > > > Well, if we didn't get the POST somewhere on the

Re: Mod_Jk2 - Default Worker

2004-02-12 Thread NormW
Good morning Costin. > NormW wrote: > > Good morning Costin. > > Apologies for the silence. I had hoped there might have been a little more > > input from others on this topic. > > Same here :-) > > > > >>However the most common case is to have at least one tomcat, and there > >>is no real benefit

Re: Mod_Jk2 - Default Worker

2004-02-12 Thread Costin Manolache
Henri Gomez wrote: Well, if we didn't get the POST somewhere on the WebServer, and if the tomcat failed to respond, we couldn't resent the whole POST to the second one. If we get the first bytes ( but not the entire POST ), we can still save them, and if the first tomcat fails - resend it. Wh

Re: Mod_Jk2 - Default Worker

2004-02-12 Thread Henri Gomez
Costin Manolache wrote: Henri Gomez wrote: jean-frederic clere wrote: Henri Gomez wrote: Costin Manolache wrote: NormW wrote: Good morning Costin. Apologies for the silence. I had hoped there might have been a little more input from others on this topic. Same here :-) We're working

Re: Mod_Jk2 - Default Worker

2004-02-12 Thread Costin Manolache
Henri Gomez wrote: jean-frederic clere wrote: Henri Gomez wrote: Costin Manolache wrote: NormW wrote: Good morning Costin. Apologies for the silence. I had hoped there might have been a little more input from others on this topic. Same here :-) We're working, Jean-Frederic, Kurt and I

Re: Mod_Jk2 - Default Worker

2004-02-12 Thread Guenter Knauf
Hi Costin, >> Good morning Costin. >> Apologies for the silence. I had hoped there might have been a little >> more input from others on this topic. I think it is also necessary to discuss a bit the proper configuration of mod_jk2. The docu is all other but clear, mixed up with the docu for mod_jk,

Re: Mod_Jk2 - Default Worker

2004-02-12 Thread Henri Gomez
jean-frederic clere wrote: Henri Gomez wrote: Costin Manolache wrote: NormW wrote: Good morning Costin. Apologies for the silence. I had hoped there might have been a little more input from others on this topic. Same here :-) We're working, Jean-Frederic, Kurt and I in arranging 2.0.4 bu

Re: Mod_Jk2 - Default Worker

2004-02-12 Thread jean-frederic clere
Henri Gomez wrote: Costin Manolache wrote: NormW wrote: Good morning Costin. Apologies for the silence. I had hoped there might have been a little more input from others on this topic. Same here :-) We're working, Jean-Frederic, Kurt and I in arranging 2.0.4 build so new features should wai

Re: Mod_Jk2 - Default Worker

2004-02-12 Thread Henri Gomez
Costin Manolache wrote: NormW wrote: Good morning Costin. Apologies for the silence. I had hoped there might have been a little more input from others on this topic. Same here :-) We're working, Jean-Frederic, Kurt and I in arranging 2.0.4 build so new features should wait for 2.0.5. BTW, I a

Re: Mod_Jk2 - Default Worker

2004-02-11 Thread Costin Manolache
NormW wrote: Good morning Costin. Apologies for the silence. I had hoped there might have been a little more input from others on this topic. Same here :-) However the most common case is to have at least one tomcat, and there is no real benefit in supporting an arbitrary name for the worker ( lb

Re: Mod_Jk2 - Default Worker

2004-02-11 Thread NormW
Good morning Costin. Apologies for the silence. I had hoped there might have been a little more input from others on this topic. > NormW wrote: > > Good morning Costin. > > Thanks for the time given to replying. > > I agree with the ideas you have given, of decoupling URI's from workers > > explic

Autoreply: Re: Mod_Jk2 - Default Worker

2004-02-08 Thread DirectXtras
>; Mon Feb 9 02:06:14 2004 Received: from cmanolache by adsl-63-202-82-219.dsl.snfc21.pacbell.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for <[EMAIL PROTECTED]>; Mon Feb 9 02:06:14 2004 X-Injected-Via-Gmane: http://gmane.org/ To: [EMAIL PROTECTED] From: Cost

Re: Mod_Jk2 - Default Worker

2004-02-08 Thread Costin Manolache
NormW wrote: Good morning Costin. Thanks for the time given to replying. I agree with the ideas you have given, of decoupling URI's from workers explicitly tied to a communications protocol, but in reality this connectivity is supported and actually gives the minimum workable configuration. But giv

Re: Mod_Jk2 - Default Worker

2004-02-07 Thread NormW
Good morning Costin. Thanks for the time given to replying. I agree with the ideas you have given, of decoupling URI's from workers explicitly tied to a communications protocol, but in reality this connectivity is supported and actually gives the minimum workable configuration. But given that a def

Re: Mod_Jk2 - Default Worker

2004-02-06 Thread cmanolache
NormW wrote: > Good morning All. > The default 'worker', which is hard-wired into Mod_Jk2, is 'lb:lb', and > is, for most users I believe, a wrong guess at best, since the majority of > users are probably not using mod_jk2 in load-balancing mode. The 'guess' > means that mod_jk2 creates uri object