Dan, Henri,
Remember the goal - to have a high quality connector and servlet
container.
Whatever brings us closer to that is good.
Right now there are 3-4 people fixing bugs and working on mod_jk - and you
2 have probably the most knowledge about it.
I was hoping that by moving it in a separate place we might get to share
and merge the connector with 4.0. And that would be good because it'll
increase the quality and the community behind the connector.
This can happen only if all of you agree ( and also Craig, Pier and Remy
who are working on connectors too on the 4.0 side ).
Everything else ( list, cvs, integration with tomcat, etc ) is detail :-)
Costin
On Thu, 15 Mar 2001, GOMEZ Henri wrote:
> >I don't see the advantages to having a separate project for
> >the connectors.
> >Can someone explain that to me?
> >
> >The main disadvantage that I see is that the connectors and
> >Tomcat are very tightly linked.
>
> Why did you want the connector and Tomcat so tightly linked ?
>
> Take for example, mod_perl, mod_rubys or mod_python.
> Did mod_perl is hardly linked to perl ? Did you mix
> developpement of perl and mod_perl ?
>
> >I think having one developer list for TC and the
> >connectors makes a lot of sense.
>
> Yes we must split user/dev connector list from tomcat (core) list.
>
> >I think having one bug
> >system for TC and the connectors makes a lot of sense (especially since
> it's not
> >always clear if the bug is in TC or in the connector when it is reported).
>
>
> if a request works against the Tomcat native http connector and didn't
> works when passing via connector, it's clearly a connector bug.
>
> >Ditto for the user list, where TC/connector configuration issues are ever
> popular.
> +1
>
> >Would this separate project include both C and Java code? It
> >would have to, if it would have any meaning (just working on one side of
> the protocols
> >would be a nightmare to sync up with a "separate" project).
>
> A connector is part of code in C (Apache, IIS, NES) and part in Java (the
> plug in
> Tomcats). No need to split here.
>
> >But if there's Java code in there, there's going to have to be different
> code for each
> >different engine which the connector talks to (e.g. TC 3, TC 4). Pulling
> >that code out of the main projects makes no sense to me. It is totally
> >dependent on the rest of the project code.
>
> Sure, TC 3 and TC 4 use differents 'Interception' mechanism but the core
> ajp12/ajp13 code
> is and must be the same.
>
> >I'm not sure if I'd want to be a committer on a different
> >project -- once 3.3 is released, I'm planning on working on the 4.x branch.
>
>
> If you remember when the tomcat 3.3 was finally decided it was asked to
> developpers to keep working on it after release.
>
> >The first thing
> >I'd like to do (which I threatened to do a long time ago!), would be to
> >write an ajp13 connector and/or merge mod_webapp with mod_jk. That is
> >"connector" work, but I, personally, am more interested in the servlet
> >engine as a whole than on "just" the connectors.
>
> I'm more interesting in building a stable connector and I'll concentrate
> on that. There is allready many talentuous developper like Costin or Craig
> (I don't forget Nacho, Larry, Remy, Pier....) to works on Tomcat core.
>
> Working on connector is important for production world (and just before
> management decision) since stable, fast and featured connectors will help
> impose Tomcat's in real world.
>
> It's my personal opinion and vision but what make me choose JServ was
> Apache mod_jserv connector with it's fault-tolerance and load-balancing.
> And only this feature make my company (and others later) choose the Apache
> solution for servlet/jsp developpment and production.
>
> Regards
>
