Jetty3/Jakarta Proposal

[Greg Wilkins <gr...@mortbay.com>]

Having thought about the best way that I can contribute effort and the
Jetty source code to the Jakarta project ( and about the best way to
use Jakarta components in Jetty),  I have put together a rough proposal
for a parallel development.

The intent is to let the Jakarta project to get on with merging JSERV 
and Tomcat while the Jetty HTTP/1.1 server is decoupled from it's own
servlet container and is upgraded to full RFC2616 compliance.
Once Jakarta actually has a code base and Jetty has it's value add
code in a decouple module, then is the time to look at adding HTTP/1.1
to Jakarta.

So here is the proposal...  comments please?

regards

-- 
Greg Wilkins<gr...@mortbay.com>          GB  Phone: +44-(0)171-4394045
Mort Bay Consulting Australia and UK.    Mbl Phone: +44-(0)7775534369
http://www.mortbay.com                   AU  Phone: +61-(0)299772395

Re: Jetty3/Jakarta Proposal

[James Duncan Davidson <du...@x180.com>]

> Oct 1999 - 3A releases:
> * separable protocol
> * Jetty2 servlets
> * RFC2068
> * Partial RFC2616 compliance.
> 
> Feb 2000 - 3B releases:
> * Jakarta servlet container.
> * full RFC2616 compliance.
> 
> Apr 2000 - 3C releases:
> * merge with Jakarta code base?

Sounds good. I'm glad to see that you are considering picking up the
Tomcat servlet container stuff for use in your server. As far as the
underlying architecture goes, there is a fair amount of abstraction in
the current Tomcat server which has been talked about. In some ways it
helps solve the same problems that you are talking about (and isn't that
far off).

It shouldn't be hard to bring Tomcat up to HTTP/1.1 compliance with such
a model -- I don't know if you want to wait until Apr 2000 -- you may
want to visit the schedule again when the code comes out and you can
take a look at things.

.duncan