On Sun, 2005-03-13 at 07:38 -0800,
davidrubin@warpmail.net wrote:[color=blue][color=green]
> > I'm currently in the process of implementing a file cache, and am
> > looking for any existing design patterns. I hadn't had much luck with
> > google, is anyone aware of a good file cache pattern (in my case, I
> > think the update:request ratio is around 1:1000000).
> >[/color]
> Your description is a little vague. What do you mean by a "file cache"?
> A cache of the contents of a single file? A cache of access handles to
> multiple files? What operations do clients of this cache require? You
> need to be more specific. /david[/color]
Ah ok, I'm sorry.. :)
The cache should consist of the contents of image files; these image
files are requested by other classes inside the system. The cache should
ideally work with 'keys' based on file locations inside the system, so
yes, this cache would probably be based on handles to multiple files.
Since it is a multi-threaded server application, the cache should be
thread-safe (and since there are far more reads that updates, ideally
should be based on lock-free/wait-free synchronization).
The thing is, this whole thing isn't /that/ hard to implement, but my
experience with patterns is that they often keep certain aspects in
consideration that i didn't consider yet ... :)
Thanks in advance,
Leon Mergen
Design pattern for file cache 
