Re: images in database... a suggestion
Re: images in database... a suggestion
- Subject: Re: images in database... a suggestion
- From: Geoff Hopson <email@hidden>
- Date: Mon, 12 Dec 2005 08:31:04 +0000
This is exactly how I did the Fortnum & Mason site - they had an extensive product catalog whose images were stored in a database. when the catalog was ready to go live, the images were exported to the file system under the web server. The web app had a runtime switch (mode = deploy) for the 'production' apps which I could use in a WOConditional (set a boolean in Application, then test on
application.deploy in the WOConditional. Developers didn't set the switch and therefore would read images from the database.
Worked well.
Shame the F&M site is no longer WO...t'was quite the nice reference point.
On 12/12/05, Sam Barnum <email@hidden> wrote:
I've used a hybrid approach before. Images are stored in the
database, but "cached" and served from the filesystem. That way, if
you wipe out the filesystem or install on a new machine, the images
are written to the filesystem again and served from there.
On Dec 9, 2005, at 11:53 AM, email@hidden wrote:
> Hello again; bad form replying to one's own post, but nevermind...
>
> I'm just wondering how iTMS serves it's content – does anybody know
> how that bulk storage/delivery mechanism works? It would be
> interesting to hear how that was done. Also, with this arrangement
> I've discussed below, I would be interested to hear if anybody has
> any criticisms of it for any purpose.
>
> cheers.
>
>
>> I've developed some classes that can stream data out of a series
>> of ordered BLOB's. This is used for a couple things in a couple
>> of my projects and it can also be used for storage of images and
>> the subsequent outbound streaming of images from a WOA. You can
>> find out more about this approach by downloading my framework and
>> reading the PDF if you are interested.
>>
> ...
>
>> I agree that it is nice to store the images in the database for
>> backup purposes as well as a few other things -- eg: tens of
>> thousands of images on disk poses issues for clustering. In this
>> way, described in the PDF, there need not be too much material in
>> memory at any one time except possibly (but not necessarily) when
>> the image is first loaded into the BLOB storage. This is because
>> it loads each BLOB up as it streams it out.
>>
>
> ___
> Andrew Lindesay
>
www.lindesay.co.nz
>
>
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list (
> 40prometheus-systems.com
>
> This email sent to email@hidden
>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden