On 2/23/06, Sidnei da Silva <sidnei@enfoldsystems.com> wrote:
On Thu, Feb 23, 2006 at 11:02:00AM +0530, Arsalan Zaidi wrote:
|    Hi
|    Just wondering if there are any plans to add the ability to distribute
|    the cache (and so keep it turned on) if accessing the DB through
|    various instances of SQLObject?
|    Just spent a few minutes going through the code so I'm not sure of
|    this is feasible, but it seems to me that one easy solution would be
|    to write the cache to a file on disk (mounted NFS disk (ram disk?)).
|    Since all instances are reading/writing the same data, there's no need
|    to turn the cache off...
|    The caching module can be redesiged to take in a caching 'strategy'
|    which looks like a dict. Internally, the strategy could implement the
|    cache as a simple dict (default) or a distributed cache through the
|    file system or a database etc.
|    Possible?
|    Regards.

I think you want to look at 'memcached'.

I'm not so sure. It seems to be that the proper place for distributing the cache data should be in the ORM itself, not the application. Scaling up then is just a matter of flipping a few config switches, instead of hacking and then retesting an entire. Using memcached would then simply be a choice made in the config file.

Hibernate handles distributed caches and seems to be pretty popular in the Java world :-)