That makes sense. When Marek explained it I didn't realise that IMG tags can't use the raw data, and needs to make a seperate HTTP request for the Headers.
Now, I understand. Unfortunately the desicion has been made to go with the database. Oh well, I can always code the scripts to store and grab from the filesystem, after if need be. Thank you everyone, who has responded. "John W. Holmes" <[EMAIL PROTECTED]> wrote in message 004d01c2be5c$631f4ea0$7c02a8c0@coconut">news:004d01c2be5c$631f4ea0$7c02a8c0@coconut... > > With regards to Marek, > > I don't see how there would be two queries, because there row > conisists of > > image properties and image data. So when i select the required row(s), > I > > will have properties and images. So it will be 1 query, of course it > is a > > big (size-wise) query. > > Hopefully you've gotten the point that this isn't true. If you store > your images in the database, it's going to make your main script execute > one query to output something like <img src="file.php?id=xxx" > ...properties...> for each image. Each one of those <img> tags will be a > separate request where file.php would pull the data for _one_ image, > send the headers and then send the data. > > ---John W. Holmes... > > PHP Architect - A monthly magazine for PHP Professionals. Get your copy > today. http://www.phparch.com/ > > -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
