You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by jean-frederic clere <jf...@fujitsu-siemens.com> on 2001/05/14 19:47:33 UTC
configure for jakarta-tomcat-connectors
Hi,
I have started a configure.in and makefile(s).in for the
jakarta-tomcat-connectors.
Currently I have just prepared it for Apache2.0 and Apache1.3, before going on I
have some questions:
- The idea is to have one configure.in in
jakarta-tomcat-connectors/jk/src/native and a makefile.in for each supported
WebServer. Does it sound Ok?
- Should I already think of using APR? - Just that some of my plateform are not
(yet) supported and I am reluctant of adding more #idef in the code -
- What should I do with the other WebServers (netscape, jni etc)?
The configure.in assumes that the Apache connectors sub-directories are
apache-1.3 and apache-2.0. I think that more consistant with mod_webapp.
Please, have a look to the attached files and make comments :=)
Cheers
Jean-frederic
UNSUBSCRIBE!!!
Posted by mo...@hiMolde.no.
cmanolache@yahoo.com:
> On Mon, 14 May 2001, jean-frederic clere wrote:
>
> > Hi,
> >
> > I have started a configure.in and makefile(s).in for the
> > jakarta-tomcat-connectors.
>
> Excelent !
>
> > Currently I have just prepared it for Apache2.0 and Apache1.3, before
> going on I
> > have some questions:
> >
> > - The idea is to have one configure.in in
> > jakarta-tomcat-connectors/jk/src/native and a makefile.in for each
> supported
> > WebServer. Does it sound Ok?
>
> Whatever is simpler.
>
>
> > - Should I already think of using APR? - Just that some of my
> plateform are not
> > (yet) supported and I am reluctant of adding more #idef in the code -
>
> One solution would be to create a common_apr and wrappers for the
> existing
> functions in common, using apr.
> All platfrom-dependent code should be in common, and we could use the
> current common in parallel with common_apr until it is stable and
> tested
> on all cases.
>
> I know apr is supposed to work everywhere and with any server, but I
> wouldn't remove the current code until it is actually tested. I'm quite
> scared of what'll happen on Windows + IIS for example...
>
> The jk_ stuff in common was supposed to be very close to APR as API,
> so maybe a better idea would be to (temporary) use
>
> #ifdev ARP
> apr_function
> #else
> jk_function
> #fi
>
> If needed, you could change the jk_ APIs to match the APR function.
>
>
> > - What should I do with the other WebServers (netscape, jni etc)?
>
> Just leave the existing makefiles in, in time someone could include that
> in the configure code.
>
> > The configure.in assumes that the Apache connectors sub-directories
> are
> > apache-1.3 and apache-2.0. I think that more consistant with
> mod_webapp.
>
> +1
>
> Costin
>
>
Re: configure for jakarta-tomcat-connectors
Posted by jean-frederic clere <jf...@fujitsu-siemens.com>.
cmanolache@yahoo.com wrote:
>
> On Mon, 14 May 2001, jean-frederic clere wrote:
>
> > Hi,
> >
> > I have started a configure.in and makefile(s).in for the
> > jakarta-tomcat-connectors.
>
> Excelent !
>
> > Currently I have just prepared it for Apache2.0 and Apache1.3, before going on I
> > have some questions:
> >
> > - The idea is to have one configure.in in
> > jakarta-tomcat-connectors/jk/src/native and a makefile.in for each supported
> > WebServer. Does it sound Ok?
>
> Whatever is simpler.
>
> > - Should I already think of using APR? - Just that some of my plateform are not
> > (yet) supported and I am reluctant of adding more #idef in the code -
>
> One solution would be to create a common_apr and wrappers for the existing
> functions in common, using apr.
> All platfrom-dependent code should be in common, and we could use the
> current common in parallel with common_apr until it is stable and tested
> on all cases.
>
> I know apr is supposed to work everywhere and with any server, but I
> wouldn't remove the current code until it is actually tested. I'm quite
> scared of what'll happen on Windows + IIS for example...
>
> The jk_ stuff in common was supposed to be very close to APR as API,
> so maybe a better idea would be to (temporary) use
>
> #ifdev ARP
> apr_function
> #else
> jk_function
> #fi
Ok, I will used HAVE_APR for this purpose.
>
> If needed, you could change the jk_ APIs to match the APR function.
Probably additing an apr_pool_t *ctx to the parameters solves most of needed
changes.
>
> > - What should I do with the other WebServers (netscape, jni etc)?
>
> Just leave the existing makefiles in, in time someone could include that
> in the configure code.
>
> > The configure.in assumes that the Apache connectors sub-directories are
> > apache-1.3 and apache-2.0. I think that more consistant with mod_webapp.
>
> +1
>
> Costin
Re: configure for jakarta-tomcat-connectors
Posted by cm...@yahoo.com.
On Mon, 14 May 2001, jean-frederic clere wrote:
> Hi,
>
> I have started a configure.in and makefile(s).in for the
> jakarta-tomcat-connectors.
Excelent !
> Currently I have just prepared it for Apache2.0 and Apache1.3, before going on I
> have some questions:
>
> - The idea is to have one configure.in in
> jakarta-tomcat-connectors/jk/src/native and a makefile.in for each supported
> WebServer. Does it sound Ok?
Whatever is simpler.
> - Should I already think of using APR? - Just that some of my plateform are not
> (yet) supported and I am reluctant of adding more #idef in the code -
One solution would be to create a common_apr and wrappers for the existing
functions in common, using apr.
All platfrom-dependent code should be in common, and we could use the
current common in parallel with common_apr until it is stable and tested
on all cases.
I know apr is supposed to work everywhere and with any server, but I
wouldn't remove the current code until it is actually tested. I'm quite
scared of what'll happen on Windows + IIS for example...
The jk_ stuff in common was supposed to be very close to APR as API,
so maybe a better idea would be to (temporary) use
#ifdev ARP
apr_function
#else
jk_function
#fi
If needed, you could change the jk_ APIs to match the APR function.
> - What should I do with the other WebServers (netscape, jni etc)?
Just leave the existing makefiles in, in time someone could include that
in the configure code.
> The configure.in assumes that the Apache connectors sub-directories are
> apache-1.3 and apache-2.0. I think that more consistant with mod_webapp.
+1
Costin