I agree that even if you have option b) working, option a) is the
correct way to go so that we don't break backwards compatibility.
The consensus seems to be in freezing ajp13 and adding new features
in ajp14 only. It will avoid conflict with servlet-engine using
standard ajp13 protocol (TC
Hi to all,
The work in still on progress on AJP14 and I've got new
questions on ajp14.
1) AJP14 could be considered like an evolution of AJP13.
Basically the same protocol but with added commands.
AJP13 use the 'AB' chars in start of protocol, what about
using something like 'DE'
a couple quick thoughts (i haven't fully processed all of this yet
:))...
feels like the right thing to do is freeze ajp13, and only add new stuff
to ajp14. perhaps code can be refactored so that common stuff in
ajp13/14 can be pulled out of the ajp13 code and put into a common place
in
](. .)
PGP KEY : 697ECEDD...oOOo..(_)..oOOo...
PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6
-Original Message-
From: kevin seguin [mailto:[EMAIL PROTECTED]]
Sent: Monday, June 04, 2001 5:48 PM
To: [EMAIL PROTECTED]
Subject: Re: More on ajp14
a couple
PROTECTED]]
Sent: Monday, June 04, 2001 5:48 PM
To: [EMAIL PROTECTED]
Subject: Re: More on ajp14
a couple quick thoughts (i haven't fully processed all of this yet
:))...
feels like the right thing to do is freeze ajp13, and only add
new stuff
to ajp14. perhaps code can be refactored so
I agree that even if you have option b) working, option a) is the
correct way to go so that we don't break backwards compatibility.
Mike Anderson
Senior Software Engineer
Platform Services Group
[EMAIL PROTECTED]
Novell, Inc., the leading provider of Net services software
www.novell.com
[EMAIL
