RE: [VOTE] Removal of mod_jk for Apache 2.0 from jakarta-tomcat f or T omcat 3.3

[cm...@yahoo.com]

I spent some quality time with emacs and merge, comparing j-t-c and j-t
versions of jk.

So far things look very good, all fixes in j-t seems to be already in
j-t-c. The only big difference ( that makes difficult to comapare ) is
ajp13, but it seems we are ok there.

Henri - could we undo the ajp13.c changes, for example by copying the
current ajp13 from j-t and re-doing the autoconf changes ? Having
ajp_common is nice, but I think we would be better if we keep
ajp13 unchanged and let ajp14 evolve without having common code
with ajp13. The protocols are not backward compatible, and they shouldn't
anyway.

Only major fixes should be merged back into j-t, the code there is stable
and it's far better to keep it that way as it reduces the pressure on
j-t-c.

You can treat this as a branch - because if we drop j-t/src/native and
use j-t-c, then we'll have to create a branch for the stable release.

Of course, the nice thing is that most changes in j-t-c/jk will happen
in ajp14 and probably a new jni connector ( that I'm planning ), so
releasing a j-t-c should be much easier ( it'll have the same stable
code as j-t, plus extra features ).

BTW, since j-t-c/jk works for both 3.3 and 4.0, it would be nice if
we could plan a release of the jk connector ( or at least milestone/alpha
or beta ) sometime shortly after 3.3 and 4.0 are out ( so it can
rely on the stable environment and be tested with it )

Costin




On Mon, 10 Sep 2001, Larry Isaacs wrote:

> Hi Henri,
>
> I appreciate your efforts concerning the connectors.  My
> position is that Tomcat 3.3 needs to have stable Ajp13
> connectors for Apache 1.3, IIS, and to the extent we
> can, Netscape.  A connector for Apache 2.0 should come out
> of jakarta-tomcat-connectors instead of jakarta-tomcat.
> Given that connectors were part of 3.2.x releases, I'm
> very reluctant to remove all of them from 3.3.
>
> Since we are approaching an attempt to release, I need to
> impose the restriction on the connectors that no features be
> added and only safe fixes be applied.  I believe this
> restriction is best imposed on the jakarta-tomcat tree at this
> time and not jakarta-tomcat-connectors where Apache 2.0 is
> ongoing.
>
> If there are bug fixes in J-T-C that would benefit the J-T
> connectors, and they are safe and easy to apply, then they
> are worth considering to port. If one is needed, but may not
> be safe, please let me know of the issue.  Otherwise, don't
> bother back porting J-T-C changes to J-T.
>
> I plan to go ahead and delete the J-T Apache 2.0 support
> once we know there isn't anything there that we need to port
> to J-T-C.  You may be the best judge as to when the deletion
> can occur.  If you could let me know, or suggest how I might
> check, I would appreciate it.
>
> I don't anticipate doing much, if any, maintenance on the
> connectors after the Tomcat 3.3 release.  So hopefully,
> this should be a temporary pain, and shouldn't be that
> painful since the J-T connectors should be stable
> already (given there is some recent work on input chunking
> that we hope to have debugged soon, perhaps already.
> Thanks Keith).  If there are issues where I shouldn't
> consider them stable, please let me know so we can
> address them.
>
> Thanks,
> Larry
>
>
> > -----Original Message-----
> > From: GOMEZ Henri [mailto:hgomez@slib.fr]
> > Sent: Monday, September 10, 2001 4:39 AM
> > To: tomcat-dev@jakarta.apache.org
> > Subject: RE: [VOTE] Removal of mod_jk for Apache 2.0 from
> > jakarta-tomcat
> > f or T omcat 3.3
> >
> >
> > +1
> >
> > Let me comment at little.
> >
> > I'm currently working in porting changes in
> > JT to JTC and from JTC to JT.
> >
> > For example, recent change in AJP13 chunk support
> > in JT are not in JTC and latest stuff for Apache 2.0.26-dev
> > not in JT.
> >
> > Let me say that it's just a nightmare to work on two branches
> > (but that's allready a known problem :)
> >
> > Could we go a step farther and concentrate on just J-T-C.
> >
> > My question is, why not working today only in JTC and make
> > use regular snapshot of JT instead of trying to maintain
> > 2 sets of code ?
> >
> > Pier is allready doing that for mod_webapp and have removed
> > (correct Pier ?) all the connector part from Tomcat 4.0 tree,
> > and is using JTC snapshot of WA at each TC 4.0 release ...
> >
> >
> > -
> > Henri Gomez                 ___[_]____
> > EMAIL : hgomez@slib.fr        (. .)
> > PGP KEY : 697ECEDD    ...oOOo..(_)..oOOo...
> > PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6
> >
>

RE: [VOTE] Removal of mod_jk for Apache 2.0 from jakarta-tomcat f or T omcat 3.3

[cm...@yahoo.com]

On Mon, 10 Sep 2001, Keith Wannamaker wrote:

> I just finished merging all the chunked encoding
> support for ajp13 into j-t-c and was about to checkin.
> I'll hold off until we decide about this:
>
> | Henri - could we undo the ajp13.c changes, for example by copying the
> | current ajp13 from j-t and re-doing the autoconf changes ? Having

If you have them, just check in. If we do this, the changes will get in
anyway ( since we have them in j-t ).

Yes, I hate duplication ...

Costin

RE: [VOTE] Removal of mod_jk for Apache 2.0 from jakarta-tomcat f or T omcat 3.3

[Keith Wannamaker <Ke...@Wannamaker.org>]

I just finished merging all the chunked encoding
support for ajp13 into j-t-c and was about to checkin.
I'll hold off until we decide about this:

| Henri - could we undo the ajp13.c changes, for example by copying the
| current ajp13 from j-t and re-doing the autoconf changes ? Having

Keith