On 28/09/2007, at 9:28 AM, Dossy Shiobara wrote:
Yes! Finally, someone else who uses the 404-handler-as-request-
processor
pattern! Indeed, you can't beat static file serving performance.
And,
My first inspiration for this came way back in the last century, from
working with Vignette StoryServer. Rather bad technology that HAD to
use caching to be able to serve more than a few pages a second, but
the way they did it was a neat trick.
The only tricky thing is to handle the "stampeding herd" situation,
where many requests for the same uncached object come in at the same
time. You only want one request to populate the cache--you want all
At the moment, there is only one server and when the file is
uploaded, I also pre-cache it. If we ever do need more servers, I am
thinking of simply having the upload process cycle through a list of
servers it then does a http request to. I plan to do a similar thing
for clearing the cache. If the request fails, you can log and queue
it for a re-try.
If the farm would get beyond two servers, it would be worth looking
into serving the images only out of two servers (for fail over); no
need to have all of the app servers keep their own copy!
Bas.
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]>
with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject:
field of your email blank.
