> CFMX standard doesn't get involved in static content at all > (i.e. anything not parsed as a CF file) so the location > should make no difference.
Actually, this isn't entirely true. By default, when you hook CF up to your web server, CF installs a module that examines each incoming request. On IIS, for example, CF installs an ISAPI filter (or an ISAPI wildcard extension on IIS 6). If a request's URL matches one of the defined patterns that CF is looking for, such as "*.cfm", the module will forward the request to the CF server itself. This URL pattern matching adds a bit of overhead to requests for static files. I'm not really sure how much it adds, to be perfectly honest. However, if you're using CFMX Enterprise on a J2EE server, you can use a separate context root just for CF requests to avoid this overhead. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ Fig Leaf Software provides the highest caliber vendor-authorized instruction at our training centers in Washington DC, Atlanta, Chicago, Baltimore, Northern Virginia, or on-site at your location. Visit http://training.figleaf.com/ for more information! ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:196417 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
