PROTECTED]]
Sent: Monday, April 30, 2001 5:53 PM
To: [EMAIL PROTECTED]
Subject: Re: porting ajp13 to tomcat 4 (was Re: ajp13 question)
If you have java ajp13 works in non-balancing mode, you've done
the hardest part !
that's encouraging :)
that's what i've decided to do. my goal is to first
On Mon, 30 Apr 2001, GOMEZ Henri wrote:
damn! i wasn't expecting that complex of an answer ;)
The difficulty is in the difference between TC 3.2/3.3 and 4.0
and the how the connector are written. They're just to highly
linked in the tomcat core !
Well, someone can reimplement the
On Mon, 30 Apr 2001, GOMEZ Henri wrote:
damn! i wasn't expecting that complex of an answer ;)
The difficulty is in the difference between TC 3.2/3.3 and 4.0
and the how the connector are written. They're just to highly
linked in the tomcat core !
Well, someone can reimplement the
Unless everyone's in a hurry to port mod_jk on TC 4 ASAP, I suggest waiting
a bit. I'll be spending time on a new connector architecture for TC 4
which will actually be very similar to the one in TC 3.3 (except hopefully
even cleaner and simpler). That should make porting mod_jk much easier
for those who are interested...
updated code for ajp13 connector for tomcat 4. this version more or
less works, but needs some major cleanup/refactoring.
i ended up copying a bunch of code out of some files in the http
connector package, and the Http*Base classes out of the connector
package.
You make a great job here and the ajp13 port to Tomcat 4.0
will be strategic for many sites.
the code isn't real pretty right now. in fact, it's downright ugly!
but that's ok, that's what refactoring is for ;) and hopefully,
somebody who knows more can help!
Refactoring could still be done
unfortunately, i have an immediate need for ajp13 in tomcat 4. i want
to move to tomcat 4, but can't without connectivity between
iis/netscape
web servers and tomcat. porting ajp13 from tomcat 3.x to tomcat 4
seemed like it would be easier than writing iis/netscape
connectors for
the
Keep up the good works. I'll test it against my mod_jk.
Which version of Tomcat 4.0 must I use, TC 4.0B3 ?
i'm using tc 4.0b3.
as i keep updating my code, what is the best way to share it? keep
posting updates to this list?
-kevin.
unfortunately, i have an immediate need for ajp13 in tomcat
4. i want
to move to tomcat 4, but can't without connectivity between
iis/netscape
web servers and tomcat. porting ajp13 from tomcat 3.x to tomcat 4
seemed like it would be easier than writing iis/netscape
connectors for
the
The documentation is wrong...IIS works with ajp13...i'll change docs
accordingly..
Saludos ,
Ignacio J. Ortega
-Mensaje original-
De: GOMEZ Henri [mailto:[EMAIL PROTECTED]]
Enviado el: martes 1 de mayo de 2001 0:04
Para: [EMAIL PROTECTED]
Asunto: RE: porting ajp13 to tomcat 4
-Original Message-
From: Ignacio J. Ortega [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, May 01, 2001 12:10 AM
To: '[EMAIL PROTECTED]'
Subject: RE: porting ajp13 to tomcat 4 (was Re: ajp13 question)
The documentation is wrong...IIS works with ajp13...i'll change docs
accordingly..
Saludos
Good.
Did there is people around using NES/IPLANET which could
confirm the status of ajp13 and NES ?
I tested it ( long ago ), both NES and IIS ( yes, I did installed windows
for that !). Ajp13 and JNI used to work fine ( JNI doesn't work very well
with Apache1.3.x, as it's not
-
HAve sense to continue naming ajp12 on IIS howto doc? i think not as
there isnt a substitute for isape_redirect.dll as mod_jserver vs.
mod_jk..so use ( or recommend ) a deprecated protocol has no sense for
me ..
ajp12 and ajp13 are both protocols used to link web-server to
tomcat. when
On Tue, 1 May 2001, Ignacio J. Ortega wrote:
Good.
Did there is people around using NES/IPLANET which could
confirm the status of ajp13 and NES ?
HAve sense to continue naming ajp12 on IIS howto doc? i think not as
there isnt a substitute for isape_redirect.dll as mod_jserver vs.
14 matches
Mail list logo
