Be carefull in using mod_jk statically.
It still changing :)
-
Henri Gomez ___[_]____
EMAIL : [EMAIL PROTECTED] (. .)
PGP KEY : 697ECEDD ...oOOo..(_)..oOOo...
PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6
>-----Original Message-----
>From: Craig O'Brien [mailto:[EMAIL PROTECTED]]
>Sent: Thursday, April 19, 2001 3:35 PM
>To: [EMAIL PROTECTED]
>Subject: RE: mod_jk
>
>
>My understanding is that nearly any module can be statically
>linked within
>apache rather then used as a DSO. (within the Apache tree vs.
>mod_jk.so)
>This must be done during the build of Apache. The trade off is larger
>instances of Apache and losing the ability to upgrade the
>individual modules
>but %20* faster loading. It is on my list of things to do but
>I have not
>tried it yet as I currently have a "happy family." I have read many
>recommendations against doing this, however, as you must thereafter
>completely rebuild Apache for every upgrade.
>
>I too am interested in any information from anyone who has
>tried this. Is
>there a performance boost? I personally find the mod_jk.so
>route to suffer
>in performance.
>
>Regards,
>Craig
>
>-----Original Message-----
>From: Wesselmann, Marcus [mailto:[EMAIL PROTECTED]]
>Sent: Thursday, April 19, 2001 4:48 AM
>To: '[EMAIL PROTECTED]'
>Subject: mod_jk
>
>
>Hi,
>
>is there a way to compile mod_jk directly into Apache, instead
>of using it
>as an .so ?
>
>Thanks,
>
>Marcus
>
