Caldarale, Charles R wrote:
From: John Laughton [mailto:[EMAIL PROTECTED]
Subject: Re: static server implementation?
I ended up created a second context in tomcat that allows
access to the static content (ie. large jpegs)
I'm confused. Why wasn't Tomcat's default servlet sufficient? It's
sole purpose is to deliver static content.
But you also get many things you might not need or want(in my case). The
default is setup to allow JSP, servlet's or whatever else can be
configured in a web.xml. 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 understand this is not the goal of a reference implementation of a
servlet container. But I think people would have a use for this for
memory saving and security.
I can see an interface like StaticHost and StaticContext that gets
extended by Host and Context.
Has this been hashed through before (can't narrow my search enough to
find out)?
Is this worthwhile for others?
best,
-Rob
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
