It seems from my research that there are high level
scalability to storing site images inside CF8/wwwroot/myApp/images
????
Specifically as <img src="images/blah.jpg"> generates a
separate http request AFTER the page is downloaded to the browser
then why not have the webserver respond with the image rather than
involving the cfAppServerr?
At present I'm developing on a WindowsServer2003 with IIS6
box that has the cf dev web server installation on it so I test
pages at
http://www.myIP:8500 (but realize
this will change upon going to production though haven't ever done
so)
Now then, at present I can save a copy of the images into
C:\Inetpub\wwwroot\images and access them via <img src="
http://www.myIP/images/blah.gif"
/> which I assume is accomplishing this but am I missing
something in terms of security/performance/ability to upload/????
Once we are no longer using port 8500 is this still possible
-- and if so how would I address the different location?
I know there are issues regarding other sites using your
images that need to be addressed but have to assume there is a way
to code the webserver (iis or apache) to disallow all access except
from
www.mysite.com ???
I've read some blogs on <cfinclude> and/or mappings
blogs
but this again seems mainly to "cost" the cfAppServer
I'm not opposed to someday need/want to move to a dedicated
machine specifically for images storage and serving but assuming a
3 Tier (webServer-CF8-database) off-hand it seems better for
redundancy to put the images on the webserver???
What about porting to flash on the front-end (I know there
are sandbox/cross-domain issues but don't know much about them)?
And finally, given the overhead of repeated separate image
requests, is there a way to combine the request for a collection of
images (whereever it goes to) into one single (HTTP) transaction?
Thanks in advance (for just reading this far if nothing else
:)