Return-Path: Mailing-List: contact torque-user-help@db.apache.org; run by ezmlm Delivered-To: mailing list torque-user@db.apache.org Received: (qmail 84069 invoked from network); 20 Mar 2003 22:41:46 -0000 Received: from owlery.vecna.com (207.188.238.194) by daedalus.apache.org with SMTP; 20 Mar 2003 22:41:46 -0000 Received: from complexity (pcpmd.vecna.com [207.188.238.201]) by owlery.vecna.com (8.11.6/8.11.6) with SMTP id h2KMfk631638 for ; Thu, 20 Mar 2003 17:41:50 -0500 Message-ID: <018101c2ef31$b4cb8d30$0f03a8c0@complexity> From: "Bill Schneider" To: "Turbine Torque Users List" References: Subject: Re: How to read/write images to/from db Date: Thu, 20 Mar 2003 17:40:21 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2720.3000 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Also from a deployment and configuration point of view, I find it easier to have fewer location-specific, external dependencies. you can get around the browser-cache issue by having a servlet that takes URLs that "look like" normal URLs with .gif, .jpeg extensions, using pathExtraInfo instead of query params. -- Bill ----- Original Message ----- From: "Scott Eade" To: "Torque Users List" Sent: Thursday, March 20, 2003 5:37 PM Subject: Re: How to read/write images to/from db > One problem with storing the images as files is that it becomes harder to > dynamically manage the security of the images if the ability to view them > needs to be controlled on a per user basis. > > Most applications won't need to worry about this though. > > Scott > -- > Scott Eade > Backstage Technologies Pty. Ltd. > http://www.backstagetech.com.au > .Mac Chat/AIM: seade at mac dot com > > > On 21/03/2003 12:17 AM, "Dan Allen" wrote: > > > It is pretty much a consensus that storing images in a database is > > an unnecessary overhead, not because the database can't handle BLOBs > > (although the relational aspect of searching and filtering is pretty > > much lost with BLOB fields) but that a browser must issue a new > > request each time you want to dish out an image because there is no > > way for the browser to make a hard cache link. You should store > > only meta data and a file reference in the database, perhaps even > > only a relative file reference in case your data storage location > > changes. > > > > Dan > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: torque-user-unsubscribe@db.apache.org > For additional commands, e-mail: torque-user-help@db.apache.org >