tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Costin Manolache <cmanola...@yahoo.com>
Subject Re: [5.0] Input optimization
Date Sun, 05 Jan 2003 18:34:44 GMT
Remy Maucherat wrote:

> Costin Manolache wrote:
>> Great !
> 
> If you could come up with a better name for the "substract" method ;-)
> It's supposed to be the opposite of append.
> 
> The optimization works good. It should help WebDAV as well as web
> services, as long as they use the Tomcat reader.

WebDAV: is there any reason to keep our webdav servlet instead of just
bundling jakarta-slide ? Can jakarta-slide use the tomcat-specific 
optimizations ( for example using some factory or hook ) ? 
 
> Hopefully, I'll be able to write the new mapper soon, 

My wish list ( if possible ):
 
- I think the new mapper should be a "global" mapper - i.e. it should
handle all aspects of the mapping, from vhost and aliases, all contexts
and up to the servlet wrapper.
This would allow more optimizations ( a tree or some other tricks ) than
the current chain of 3-4 hashtable mappers ( one for host, one for ctx, 
one for servlet ). 

- Add/remove mapping should be propagated via coyote actions - someday
jk may intercept the events and inform the native side when a new webapp
is added.

- there is an interesting optimization in 3.3 - once a jsp is compiled,
a prefix mapping is added and the behavior is identical with precompiled
jsps ( i.e. no jsp servlet or extra overhead - it is a regular servlet ).
( the reloading checks are a different story - they can be handled by the
generated servlet or some other module )

Costin




--
To unsubscribe, e-mail:   <mailto:tomcat-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:tomcat-dev-help@jakarta.apache.org>


Mime
View raw message