Sorry for the late reply on this.  I'd also like to help out with
mod_jk2 and this move to apr.  Mostly for the sake of the NetWare
platform, though I need to understand the Linux connectors well as well.

Let me know where I can be of service.  I have a little experience with
the connectors, though mostly mod_jk.  I will do my best to get up to
speed on it though and help out.

Jeff Tulley  ([EMAIL PROTECTED])
(801)861-5322
Novell, Inc., The Leading Provider of Net Business Solutions
http://www.novell.com
>>> [EMAIL PROTECTED] 10/17/03 5:41 AM >>>
+1

I can help out.

This is a significant change for a minor revision to 2.0.4,
perhaps we should bump it to 2.1 or even 3.0?

Glenn

Henri Gomez wrote:
> Ok, about everybody seems to agree on using apr for jk2
> (still waiting Nacho for IIS).
> 
> APR side will be to :
> 
> - Update doc to indicate that APR is mandatory
> 
> - Remove #idef APR
> 
> - Use APR for all OS operation and sus will save us from
>   handling all the #include for all the diverses IO operation
>   (it's really a pain).
> 
> - For now still use_jk pool, but the version using apr_tools.
> 
> - Make socket use apr_socket for compatibility.
> 
> 
> JK to JK2 fonctionnalities backport :
> 
> - Check features added in jk and not present in jk2 (ie cping/cpong).
>   There was also some specific lb workers settings which should be
>   studied.
> 
> - After this works, make a 2.0.4 release and start extensive
>   testing.
> 
> 
> On the channel side I added a new method, hasinput which should help
> use determine if there is something to do on 'stream connections'.
> 
> For instance, it's used in jk/jk2 by the cping/cpong stage when
> connectTimeout, prepostTimeout and replyTimeout are set.
> 
> 
> And no the who's who ;)
> 
> I'd like to know who could works on jk2 evolution.
> 
> BTW, where could we find today the jk/jk2 documentation which is
> regenerated each day  ?


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to