I have wrestled with this question the past couple of days. I have searched the archives, and saw the same question asked in January 2001, without beeing answered. So I give it a go again: What is the optimal placement of static content (html, gif's, js files) in a external web server/JRun configuration? We are using IIS as the external web server. My findings so far points to three possible approaches: 1. You can create a normal web application (additional web application) in JRun and place the static content below that (for example alongside the WEB-INF folder). Every static content file will then be served by JRun's FileServlet. Scott Stirling said in a post on this list in early January 2001 that this is the slowest way. 2. The other option is to "mark" the application as a default web application, in contrary to the additional web application from the example above (these two terms are defined in devapp.pdf page 72 from the JRun 3.1 docs), by setting the <web-app-name>.use-webserver-root=true parameter in local.properties of the server (and/or webapp.properties for the actual web application?). This will cause the JRun connector to skip the JRun roundtrip for static content, and lett IIS serve this content. Scott Stilring stated that this was much faster than option 1. This approach has one major limitation: - Only one can exist per "site" in IIS, since you define web server document root pr "site" in IIS. This means only one can exist per server in JRun, since each JRun Server needs a separate IIS site. This is not good for development/testing purposes at least. Cost conscientious production use neither. 3. One can set up an intricate scheme of virtual directories in IIS, mapping the static content for each web application outside of JRun's "reach", letting IIS serve the content. Any suggestions? Other approaches? What is the best approach for a high performance AND flexible setup? ~ Tormod ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~- Tormod Hystad Senior Developer, R&D CatalystOne, Inc. - Execution excellence! ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
