mod_jk should be compiled statically in Apache but nobody
asked for that feature previously since mod_jk as still
not the maturity of other well known modules like mod_index.

A feature which may be added to mod_jk, but I'd like to see
before autoconf stuff added :)


-
Henri Gomez                 ___[_]____
EMAIL : [EMAIL PROTECTED]        (. .)                     
PGP KEY : 697ECEDD    ...oOOo..(_)..oOOo...
PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6 



>-----Original Message-----
>From: Bojan Smojver [mailto:[EMAIL PROTECTED]]
>Sent: Tuesday, April 10, 2001 10:32 AM
>To: [EMAIL PROTECTED]
>Subject: Re: mod_webapp, mod_jk etc.
>
>
>Forgot to ask, would you be interested in instructions/simple shell
>script for building mod_jk as a statically linked Apache module?
>
>Bojan
>
>Dan Milstein wrote:
>> 
>> I can't speak to mod_webapp, but a mod_jk response:
>> 
>> > - I understand the need for the TCP connections to be persistent in
>> > mod_jk and mod_webapp, but I'm not sure why another 
>connection wouldn't
>> > be attempted after the reuse of the previous connection fails;
>> 
>> This was just added to the 3.3 branch (by Henri) for mod_jk 
>-- if the Apache
>> plugin detects a dead connection, it opens a new one (so you 
>don't have to
>> restart Apache when you restart Tomcat).  Needs testing, but 
>it's in there.
>> 
>> -Dan
>> --
>> 
>> Dan Milstein // [EMAIL PROTECTED]
>

Reply via email to