Hello and thank you for reading my post. My question is about configuration descriptors and how Tomcat deals with a lot of them.
I have been thinking about a solution for a problem I have to solve. This solution would involve the creation of possibly a lot of configuration descriptors. -- About "configuration descriptors" (just to make sure we are talking about the same thing) -- (In my case) the configuration descriptors are XML files which contain only one XML "context" element. They are very simple. For example: Name --- webapp#confdescr1.xml Contents --- <Context docBase="/somewhere/on/the/filesystem" /> Location --- "webapp#confdescr1.xml" is put in "/etc/tomcat6/Catalina/localhost/" Then, suppose that there is a file "my_file.txt" in the directory "/somewhere/on/the/filesystem/", Tomcat can serve it via the URL "http: //localhost/webapp/confdescr1/my_file.txt". -- My questions are: -- Is Tomcat going "to behave nicely" (that is to say answer quick enough) if it has hundreds (even thousands) of configuration descriptors to deal with? If a user wants to download the file "http: //localhost/webapp/confdescr1/my_file.txt", is it going to have to wait a long time while Tomcat is looking for the configuration descriptor "webapp#confdescr1.xml" to be able to serve the file "my_file.txt" stored in "/somewhere/on/the/filesystem/"? Does Tomcat implement a mechanism to find a configuration descriptor quickly, like an index? I hope my question is clear enough. Best regards. -- View this message in context: http://tomcat.10.x6.nabble.com/Lots-of-configuration-descriptors-tp5022940.html Sent from the Tomcat - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
