You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by cm...@yahoo.com on 2001/11/21 18:58:04 UTC
Jk and APR
This has been discussed many times, and the only conclusion was that we
should and will change mod_jk to use APR, but no clear plans were decided.
My proposal is quite simple and require minimal code change. Mod_jk
consist of a number of interfaces. We already added a channel interface
that will abstract the communication ( which is where most of the platform
dependent code is ). None of the interfaces is OS-dependent - only the
implementations.
So for all new code/workers/channels we can use APR. Mod_jk will still
work without APR ( at least in the near future ), but not all features
will be available.
For the build process: we should use apr as a regular library. We'll
use whatever is built into apache2.0, without modification.
APR is supposed to eliminate the need for OS-specific code and configure -
that means we can use a simpler makefile ( and/or the new ant based
build).
Does it sounds reasonable ?
Costin
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Jk and APR
Posted by Gomez Henri <hg...@slib.fr>.
En réponse à cmanolache@yahoo.com:
+1
I know somebody who will be happy with that.
But we should be carefull with APR.
We could use the one from Apache 2.0 when mod_jk
is compiled against AP2.
What should we use when compiling against Apache 1.3 or
IIS, NES ?
JF Clere will give us here precious advices.
Nota that APR is one of the major problem people
encounter with mod_webapp. They have more problem
finding a built APR for their system than to build
webapp really.
In my opinion, we should get only Apache 2.0 tagged APR,
ie for us today consider the one from Apache 2.0.28 beta
>
> This has been discussed many times, and the only conclusion was that
> we
> should and will change mod_jk to use APR, but no clear plans were
> decided.
>
> My proposal is quite simple and require minimal code change. Mod_jk
> consist of a number of interfaces. We already added a channel
> interface
> that will abstract the communication ( which is where most of the
> platform
> dependent code is ). None of the interfaces is OS-dependent - only the
> implementations.
>
> So for all new code/workers/channels we can use APR. Mod_jk will still
> work without APR ( at least in the near future ), but not all features
> will be available.
>
> For the build process: we should use apr as a regular library. We'll
> use whatever is built into apache2.0, without modification.
> APR is supposed to eliminate the need for OS-specific code and
> configure
> -
> that means we can use a simpler makefile ( and/or the new ant based
> build).
>
> Does it sounds reasonable ?
>
> Costin
>
>
> --
> To unsubscribe, e-mail:
> <ma...@jakarta.apache.org>
> For additional commands, e-mail:
> <ma...@jakarta.apache.org>
>
-
Henri Gomez ___[_]____
EMAIL : hgomez@slib.fr (. .)
PGP KEY : 697ECEDD ...oOOo..(_)..oOOo...
PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Jk and APR
Posted by co...@covalent.net.
On Thu, 22 Nov 2001, jean-frederic clere wrote:
>
> I would even use APR to build mod_jk: APR of httpd-2.0 (installed or source)
> otherwise the one given by --with-apr parameter with configuring mod_jk :)
I'll go ahead and create an APR directory. To keep things simple and clear
I'll not touch configure - build.xml will detect if APR_INCLUDE/apr.h is
present and compile the apr-dependent files.
The APR code will be entirely optional for now - when we are comfortable
and everything is tested we can deprecate the current platform-specific
code ( or leave it in - it doesn't hurt and people who have any problem
will have a fallback )
> The actual makefiles logic is a bit too complex I think there should be more
> targets to remove the automaticly generated makefiles.
Is there any reason we don't use GNU make ? This would allow many
simplifications in the build files ( the VPATH is one clear one, we could
also simplify a lot by using the many functions available in gmake ).
I would also like to have built.properties included in the Makefile - it
would allow a consistent mechanism of setting preferences ( paths, etc )
( i.e. consistent with tomcat and other jakarta projects ). Not sure how
difficult it would be, but when we switch to APR we'll have no reason to
use configure - everything is supposed to be portable !
> But is it is still necesary to keep native makefiles when we have a new _nice_
> tool?
For a while, yes, it's better to have a smooth transition. And we first
need to make sure everyone is comfortable with a new build system.
Costin
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Jk and APR
Posted by jean-frederic clere <jf...@fujitsu-siemens.com>.
cmanolache@yahoo.com wrote:
>
> This has been discussed many times, and the only conclusion was that we
> should and will change mod_jk to use APR, but no clear plans were decided.
>
> My proposal is quite simple and require minimal code change. Mod_jk
> consist of a number of interfaces. We already added a channel interface
> that will abstract the communication ( which is where most of the platform
> dependent code is ). None of the interfaces is OS-dependent - only the
> implementations.
>
> So for all new code/workers/channels we can use APR. Mod_jk will still
> work without APR ( at least in the near future ), but not all features
> will be available.
>
> For the build process: we should use apr as a regular library. We'll
> use whatever is built into apache2.0, without modification.
> APR is supposed to eliminate the need for OS-specific code and configure -
> that means we can use a simpler makefile ( and/or the new ant based
> build).
>
> Does it sounds reasonable ?
It does.
I would even use APR to build mod_jk: APR of httpd-2.0 (installed or source)
otherwise the one given by --with-apr parameter with configuring mod_jk :)
The actual makefiles logic is a bit too complex I think there should be more
targets to remove the automaticly generated makefiles.
But is it is still necesary to keep native makefiles when we have a new _nice_
tool?
>
> Costin
>
> --
> To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>