Howdy,Jakarta could have a minimal Tomcat binary + a set of standard Jakarta add-on web-apps. Add a "standard web app catalog viewer" to Tomcat and you're set. Right?
I don't think small market shares or lack of clients is a reason fornegative
exclude
a server feature. They are separate. If the WebDAV app added some
impact to the tomcat server, then take it out, but if not, then letsadd it
back in.
Even if WebDAV is useful in the general sense (I tend to agree with Senor Holle that it's not, I don't feel strongly either way), I think it's telling that no one complained when we removed it. Anything we add that's not used is bloat by definition, and more for us to maintain.
Of course, we already do have a WebDAV servlet shipping with tomcat5, and that's the main part. What else did you (Mark T.) think of adding to the distribution?
This gets me thinking again of the idea of a minimal build: no webdav,
no CGI, no examples, no docs, no balancer, minimal server.xml as the
default, etc, so as to minimize download size and cater to those users
who know what they're doing and just want to drop their webapp into
tomcat.
[At that point Tomcat would be kind of like what NetBeans tries to be in this regard, which is pretty nice -- all other aspects of NetBeans aside.]
-- Jess Holle