> As long as all the servers use the
> same physical path, then it's a no brainer.

well, for now, it might look no brainer. but in the future, i can move
the images to another
servers with few changes on dns configurations (i think so)..

On 7/11/08, Robert Cummings <[EMAIL PROTECTED]> wrote:
> On Fri, 2008-07-11 at 07:55 +0800, paragasu wrote:
>> what  Robert suggest, is something exactly what the big-big photos
>> gallery out there used
>> to store their image. Distributing the image into many servers. But i
>> am not very sure, how
>> they store the image location information inside the database.
>>
>> But i like the idea of using imageUId to determine where to store the
>> image.
>> I think, storing image in a bucket with 100 images each can make the image
>> more
>> manageable..
>>
>> thanks for that idea..
>
> That physical location on the hard drive just needs to be a
> configuration variable for the site. As long as all the servers use the
> same physical path, then it's a no brainer.
>
> Cheers,
> Rob.
> --
> http://www.interjinn.com
> Application and Templating Framework for PHP
>
>

-- 
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to