Re: images in databases
Re: images in databases
- Subject: Re: images in databases
- From: Pierre Frisch <email@hidden>
- Date: Fri, 25 Feb 2005 11:46:10 -0800
Bill,
Bill I disagree with you on that one. The only reason for not storing
the images in the db is because WO does not support it very well. There
are a number of way you can improve WO to make it behave and I have
done it successfully, if only Apple could listen and fix it for
everyone we would not have that discussion every few months. On the
other side having the images outside of the database essentially
destroy the initial reason for having a database. The drawback of
having operational information on two different repositories (db and
file system) are not negligible in particular backup, security and
synchronization issues.
Pierre
On Feb 24, 2005, at 13:16, email@hidden wrote:
On Feb 24, 2005, at 1:07 PM, Jeremy Matthews wrote:
Any arguments pro/con storing images inside a database vs.
referencing them inside some protected folder in a webserver itself?
Images not as in a wrapper...think inventory and such.
Yes. Don't do it. The cons vastly outweigh the pros and, from a
security perspective, you are pretty much toast anyway if someone
cracks your webserver.
A much longer response from the archives:
http://www.wodeveloper.com/omniLists/webobjects/1999/msg03936.html
_______________________________________________
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
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:
This email sent to email@hidden