On Mon, 14 May 2001, Bruce Butterfield wrote:
> What would be the major issue of adding HTTP 1.1 capability to Tomcat
> 3.2.x? Our application uses Tomcat standalone because there is almost no
> static content and thus using the Apache server seems superfluous. We
> expose SOAP-like APIs to the application and performance would certainly
> get a boost from a persistent client-server connection. I know Tomcat
> 4.x implements HTTP 1.1 but 4.x is definitely a work in progress. Any
> ideas?
Backporting the http1.1 implementationf from 4.x to 3.x is not difficult,
and can be done as a standalone module ( i.e. even for 3.2.2, you don't
need another release ). I would do it for 3.3 - but I don't have the time
and I don't think it's a big priority ( since you can use Apache or any
other "real" server for HTTP/1.1 ).
If you want to do that - I'll be happy to help. A good place to do the
work might be the jakarta-tomcat-connectors ( since HTTP/1.1 is just
another connector, like ajp ). ( or sourceforge :-)
Costin
