Well, maybe you're right (there are a lot of cons to storing images in
a database, but also a lot of pros), but independent of that
discussion: is Cake's caching capable of doing it and how should I do
it?
X-Google-Language: ENGLISH,ASCII-7-bit
Received: by 10.11.53.63 with SMTP id b63mr132995cwa;
Mon, 22 May 2006 12:07:47 -0700 (PDT)
X-Google-Token: ZGKqVAwAAACxnN4wKvjQruMx96wlCJeX
Received: from 213.93.219.26 by j55g2000cwa.googlegroups.com with HTTP;
Mon, 22 May 2006 19:07:47 +0000 (UTC)
From: "2000Man" <[EMAIL PROTECTED]>
To: "Cake PHP" <[email protected]>
Subject: Re: Image Caching
Date: Mon, 22 May 2006 19:07:47 -0000
Message-ID: <[EMAIL PROTECTED]>
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
User-Agent: G2/0.2
X-HTTP-UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; nl; rv:1.8.0.3)
Gecko/20060426 Firefox/1.5.0.3,gzip(gfe),gzip(gfe)
Mime-Version: 1.0
Content-Type: text/plain
Well, maybe you're right (there are a lot of cons to storing images in
a database, but also a lot of pros), but independent of that
discussion: is Cake's caching capable of doing it and how should I do
it?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Cake
PHP" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/cake-php
-~----------~----~----~----~------~----~------~--~---
