On 24/11/2009 12:34, Robert Koberg wrote:

On Nov 24, 2009, at 4:30 AM, Robert Koberg wrote:


On Nov 24, 2009, at 4:12 AM, Pid wrote:

On 24/11/2009 11:57, Robert Koberg wrote:

On Nov 24, 2009, at 3:09 AM, Peter Crowther wrote:

2009/11/24 TheGrailer<ken...@gmail.com>:
The most compellig argument from the "Apache2 and Tomcat 6"-friend was
indeed the static content part.

http://tomcat.markmail.org/message/il33wqqjb2dok6xz might be
illuminating - along with the discussion around it on that thread.  I
suspect Chris will be making his own comments on this thread, as he
knows his benchmarking results better than anyone!

But also confing like virtual hosts (hard in
pure tomcat?)

Easy in pure Tomcat.  Outlined at
http://tomcat.apache.org/tomcat-6.0-doc/virtual-hosting-howto.html
(assuming version 6.0.x).

It would be easier if you could keep your host configuration separate from the 
server.xml, similar to contexts. For example, the file system would look like:

-tomcat
  |-conf
    |-server.xml
    |-Catalina
      |-locahost.xml (the host config)
      |-localhost
        |-webapp1.xml
        |-webapp2.xml

Hmmm... wonder how ward it would be to implement this? Do you see any problems?

You might be able to achieve it with XML includes.

I recall previous discussion on the list describing this as possible - why not give 
it a try&  report back?


Yes, I remember. I think I was going to look at it back then :)

The problem with XML Include or (even worse) DTD defined entities is that if 
the included file is changed (the host files are set to be watched, because it 
would not appear the server.xml has changed) it would currently need to 
reconfigure the whole server (I think). It would be better if tomcat could 
recognize just one host haas changed and reload it. Haven't had a major itch 
here, so just throwing it out :)


Additionally, if you added a new host, you would need to edit the server.xml to 
add a reference to it. It would be much nicer if it worked like context config 
files. The file system currently being used for tomcat seems perfectly set up 
for such a thing.

I don't believe that the config parser can cope with making dynamic changes to the server's structure. It is possible to make fairly significant changes via JMX.


p


best,
-Rob



best,
-Rob





---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Reply via email to