Caldarale, Charles R wrote:
From: Robert Koberg [mailto:[EMAIL PROTECTED]
Subject: Re: static server implementation?
If you have a need for many virtual hosts, but do not need
or want any ability for dynamic activity it would make sense
to have a limited version of a tomcat host/context. I mean,
I have a need to create VHosts from java, but those VHosts
should not be able to affect anything (Read Only).
I'm still not understanding why a standard Tomcat isn't sufficient. If
you don't configure any dynamic content capabilities, none will
magically appear to thwart your goals.
Sure they will. There are defaults hardcoded in the implementations. Not
trying to get too far into my app, but I have need for a host and
context that has all access, say a manager app. The manager app creates
hosts that should only be read only and not share the Server defaults or
settings.
Are you concerned about
performance? Have you tested a static-only Tomcat to see if it's
adequate for your needs?
My app is a CMS. I want to allow someone to signup and start creating
content or a website. I want to give them a context to base their
resources of off. I don't want to give them the ability to run dynamic
stuff.
I can create my own implementation, I was just curious if something exists.
thanks,
-Rob
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
