Duplicate libraries wasting some extra memory is a tiny penalty compared to
being trapped, unable to upgrade web service when another service relies on
the same library(and is incompatible with newer versions). (Or replace
service with webapp)
-Tim
Javier Gonzalez wrote:
Actually, I don't - this server provides web services only and *very
small* set of reports pages, so going through the hassle of setting up
Apache in front of tomcat wasn't deemed to be worth it.
It doesn't have any impact on performance? I would have thought that
multiple contexts would eventually lead to duplicated libraries which
would ultimately lead to wasting memory.
Thanks for taking the time to answer my question.
On 6/7/06, Tim Funk <[EMAIL PROTECTED]> wrote:
From a performance point of view - it doesn't matter.
From a maintenaince point of view - I prefer many lean clients. That
way -
if one of them behaves badly - off they go into a new JVM (assuming
you have
apache in front of tomcat)
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
