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?

Reply via email to