Jim Jagielski wrote:
>
> On Sep 14, 2007, at 2:49 PM, Costin Manolache wrote:
>
>>
>> It may also have some implications on other use cases - deployment ( the
>> current pattern
>> is that all files for a webapp are in one place ), replication ( i.e. if
>> someone wants same webapps
>> on a pool of servers ).
>>
>
> To me this is an important point... the beauty of
> webapps is that, well, they are self contained.
>
> But I can also easily see the advantage, from an admin
> and even developer PoV for more flexibility.
>
> Basically, of course, Aliases are runtime configurations
> of what could be done via file-system provided symlinks...
> So the security and API issues should see what, if anything,
> can be gleamed from that...
Yes, this is hard to compare to httpd, as in the case of Tomcat, there
is precise specification which defines a portable web application
packaging. I see the latest changes have all aimed at breaking
portability, and I don't like that at all.
Rémy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
|