"Remy Maucherat" <[EMAIL PROTECTED]> wrote:
> Extensibility capabilities will be added to Coyote, as well as JMX management
> features, and if possible, addional protocol handlers (like WARP 1.0).
As far as I would like to see WARP and its future development, it'll
probably end up following a different container architecture. The
extenization of the HTTP stack from the core of the container brings some
advantages to the engine, but as well this need to introduce a different
layering scheme for the components, such as the removal of <Host>.
Plus, for security reasons, I want WebApp to follow the trend of being
slimmer, therefore not inheriting the whole "Tomcat" weight, but letting it
do only _the_ container, with no kits or caboodle attached to it... Apache
is my platform, there is where I will want and add complexity. Tomcat, just
a servlet container (IMO)...
This is where I want to end up to. Frankly at this point in time I don't
think that carrying on with the development of components such as the HTTP
connector, or other tomcat "features" (GZIP on-the-fly compression, CGI
support, JMX support), matters to me...
I want, and I'm getting there, only a servlet container able to handle some
10/15 millions servlet-based requests/day. Therefore also approaches such as
JNI are definitely out for high availability approach...
Given the latest developments, I seriously don't think I want to be carrying
on with TC5.0 anymore, I'll just (as always) do what matters to me, and if
it works for me, I'm set...
Pier
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
