On Mon, 18 Jun 2001, kevin seguin wrote:
> i think that soon, all of the core ajp java code should be refactored
> into the org.apache.ajp package. that probably just means removing
> Ajp13.java from org.apache.ajp.tomcat33.
It would be better to just add a note that the package is deprecated and
will be removed - for now the code is used as the "stable" version for
3.3.
We could also tag the workspace and keep the stable code in a branch, but
it' much safer to use 2 packages (same as we do with jasper/jasper34 ),
this way we can also reduce incompatibilities.
I think we should use coyote as a basis, but there are few API problems we
should fix ( I sent a mail last week about some of the problems ). In
particular I'm very interested in the event/listener model for
communication between layers.
Costin
>
> also, i think that org.apache.ajp.AjpRequest can either be replaced by
> org.apache.coyote.Request, or it should extend or adapt
> org.apache.coyote.Request.
>
> hopefully, in the coming weeks, i'll have more time to spend on this
> stuff :)
>
> -kevin.
>
> GOMEZ Henri wrote:
> >
> > Hi to all,
> >
> > I'd like to know what's the current status of ajp java on j-t-c.
> >
> > 1) We have now two implementations of AJP13 protocol,
> > in org.apache.ajp.tomcat33 and org.apache.ajp
> > Also implementations came with its own code for core engine.
> > (org.apache.ajp.tomcat33 / org.apache.ajp.tomcat4)
> >
> > Could we at minina, share ajp networking code between TC33/TC40 ?
> >
> > Will we use Coyote as base of reflexion and have implementation
> > on both TC33 and TC40 ?
> >
> > All these questions since I'll start to write ajp14 java side and
> > need to know what will be the base. If we could have at least common
> > ajp networking code between TC33/TC40, it will avoid duplicate and
> > error.
> >
> > Regards
>
