request to create the cache: you can have a cache manager begin at
application initialization that creates/checks all the images.
That way you eliminate the issues with the check/file create completely.
Personally I've never really seen the need for this, but if you're worried
about the first call problem this will solve that.
Jim Davis
_____
From: Philip Arnold [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 26, 2004 2:29 PM
To: CF-Talk
Subject: RE: How do you store a image
> From: Jim Davis
>
> However on the web side you should, for performance, not be
> constantly pulling this information from the DB, it's slow
> and wasteful. So what I do is check the DB for the image(s)
> and then check the file-system - if the image doesn't exist I
> place a cached copy of the image on the file-system and call
> it from there.
My problem with this is the speed problems
If you're running on Windows, then it can take it up to many seconds (at
times) for it to finish writing the file and updating the file system
By the time that it's passed the page to the user, the file might not be
finished, so the image will be unavailable (lovely little red X's <g>)
_____
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
