Re: [5.0] [PROPOSAL] Removing all old mappers

[Costin Manolache <cm...@yahoo.com>]

Remy Maucherat wrote:

> I've adapted the mapper to do the job of the context mapper. This will
> be used in the request dispatcher.
> 
> On a broader perspective, the idea is to get rid of the old mapper
> design, support classes, etc.
> One of its goal was to support multiple protocols (more that one mapper
> per container). However, this turned out to be a non-goal (IMO), given
> that it doesn't comply with the behavior of the only non HTTP protocol
> used which I know is being used in a servlet container (SIP). The
> problem is that for one request, SIP can map many wrappers, and invoke
> them sequentially. That model, of course, doesn't fit too well with the
> Container map(...) method. So in the end, if it's just for mapping HTTP
> like requests, it can be done in a simpler and more efficient way (see
> the mapper in j-t-c/util).
> 
> Mapping is only needed:
> - when the request gets out of the connector (done)
> - for request dispatcher mapping
> The Catalina Mapper is right now only used for request dispatcher mapping.
> 
> Mapping is a performance problem in the current request dispatching
> implementation (that and the filter mapping, which is more generic and
> easier to optimize, since it's not as tightly embedded into the Catalina
> core design).
> 
> My plan would be to:
> - Remove all current Catalina Mapper, implementations and APIs
> - Use the j-t-c/util mapper instead
> - Optimize filter mapping

+1

I don't think we'll see any "backward compatibility" problem - but in case 
anyone was using the old mapper, we may have to do something.



Costin


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