howdie,
i was wondering. i'm developing a backend that will be under some intense load in the long run.
all the data is handled is such a way that the viewer cannot see anything unless it is sent from the main 'core', which is completely unaccessable except by the only file they can access (if that makes sense).
in regards to images, this can cause issues! all page templates are stored out of reach of the client and are sent via the php coding. there is no problem with this. using a template engine and a simple 'image.php?filename=blah.gif' it's easy to make all image references in the html output to point this image getter thingy... yuh!
i was wondering (depending on what server software it is being run on [IIS, APache etc]) whether it would be more efficient at high load to use several image.php files or not........
ie, would it be faster to have image1.php image2.php image3.php so that the server is requesting 3 different files instead of sending 3 requests to one file...... if that makes sense....
ta!