>In a word - DON'T - you shouldn't get image data from a database for 2
>reasons;
>Firstly, the OS probably won't have written the file by the time the web
>server requests it
>Secondly, if 10 people ask for the same file, each will have to be written,
>displayed and killed later
>
>It's easier to have a reference to the file and just put that in the IMG SRC
Thanks for the reply. BUT, like I said it really is fine in this situation.
If I have to go in to all the details, I will. first of all, if I stored
the images on disk instead
of in a database, I would have to find a way to instantly replicate them
to all servers in the cluster. One way that has been mentioned before is to
use UNC (?) to point all the other servers to one server, so they all have
a shared drive (\\server1\sharename). BUT this still leaves a single point
of failure, negating the value of going to all the work of clustering.
Also, images will only be *stored* in this database, they will rarely be viewed
from here. Usually they will be written to static files on disk once per day
or so, and then the general public views the images from the static files on disk.
BUT, there is the need for the abiltiy to preview an image, this will be a less
often used function, the load will be minimal. So for that function, its easiest
to just pull the image directly from the database.
Any ideas? Thanks,
Ryan
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
