That's why my generic cache interface is intended to be a front-end to different cache implementations, with a common interface, and some tools built on top of that interface (such as memoizing functions).
Yes, I understand the philosophy, but before you can make a generic API, one should study several concrete examples and generalize from their needs. Currently, you have a single example (your own memcached). So I'm a little wary...
-- Dan _______________________________________________ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
