I wasn't trying to hijack the thread. I was asking a serious question
related to the previous post.
Thx for all the responses!
On Jun 7, 5:17 am, "Chris Hartjes" <[EMAIL PROTECTED]> wrote:
> Thread hijacking isn't nice...
>
> On 6/6/07, Allen Romero <[EMAIL PROTECTED]> wrote:
>
>
>
>
>
> > Is t
Thread hijacking isn't nice...
On 6/6/07, Allen Romero <[EMAIL PROTECTED]> wrote:
>
> Is there a good example of how to upload an image to the server and
> serve it up, etc?
>
> thx in advance,
>
> allen
>
> On Jun 6, 2:38 pm, AD7six <[EMAIL PROTECTED]> wrote:
> > peterhf wrote:
> > > I have bee
owledge.
>
> BAKE ON!
>
> blog: http://www.MarianoIglesias.com.ar
>
>
> -Mensaje original-
> De: cake-php@googlegroups.com [mailto:[EMAIL PROTECTED] En nombre
> de Tane Piper
> Enviado el: Jueves, 07 de Junio de 2007 04:11 a.m.
> Para: cake-php@googlegroups.com
> Asunto:
ON!
blog: http://www.MarianoIglesias.com.ar
-Mensaje original-
De: cake-php@googlegroups.com [mailto:[EMAIL PROTECTED] En nombre
de Tane Piper
Enviado el: Jueves, 07 de Junio de 2007 04:11 a.m.
Para: cake-php@googlegroups.com
Asunto: Re: Working with image files
I have a modified upload
I have a modified upload behavior I can share, although I don't have
the latest version up - but I can have it up a few hours.
The upload behavoir can upload any filetype (currently I use it for
images and MP3's) to any subdir under the webroot. Its current
features also include correcting filen
On Jun 7, 12:14 am, "Samuel DeVore" <[EMAIL PROTECTED]> wrote:
> If you do the image in db first then you can do an easy optimization later
> and look really brilliant because it serves them so much faster ;) On the
> other hand it is easier to control access to images when they are not just
>
Is there a good example of how to upload an image to the server and
serve it up, etc?
thx in advance,
allen
On Jun 6, 2:38 pm, AD7six <[EMAIL PROTECTED]> wrote:
> peterhf wrote:
> > I have been influenced by the argument given a sites such as
> >http://cakebaker.42dh.com/2006/04/15/file-upload-
If you do the image in db first then you can do an easy optimization later
and look really brilliant because it serves them so much faster ;) On the
other hand it is easier to control access to images when they are not just
sitting where apache can toss them on any old image site it wants.
On 6/6
Thank you both for your insite and opinions. They are greatly
appreciated.
After struggling for a day with the image-in-the-database paradigm,
I'm going to try the image-in-the-directory paradigm!
Regards,
Peter -
On Jun 6, 2:38 pm, AD7six <[EMAIL PROTECTED]> wrote:
> peterhf wrote:
> > I have
peterhf wrote:
> I have been influenced by the argument given a sites such as
> http://cakebaker.42dh.com/2006/04/15/file-upload-with-cakephp/. There
> is a logic to me, that having the image and the data surrounding the
> image are in one place, not devided between two places which would
> requi
I have been influenced by the argument given a sites such as
http://cakebaker.42dh.com/2006/04/15/file-upload-with-cakephp/. There
is a logic to me, that having the image and the data surrounding the
image are in one place, not devided between two places which would
require attention to not allowi
On 6/6/07, peterhf <[EMAIL PROTECTED]> wrote:
>
> I am developing a community site in which members can upload photos of
> themselves for display on their page. My plan is to store the image
> files in a database. When a photo is need for display, it is retrieved
> from the database and stored in
12 matches
Mail list logo