I think this is important too, however, I am afraid that castor's cache
interface is not open enough. Is there a way to invalidate an object from
the cache?
----- Original Message -----
From: "Wes Biggs" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, March 08, 2002 5:53 PM
Subject: [castor-dev] Distributed cache management
> Hello, I'm new to the list.
>
> I was reviewing some conversations in the archives regarding distributed
> cache management -- at one point it was suggested that a whitepaper
> describing the options be created.
>
> I need to use Castor JDO in a distributed, non-EJB environment --
> multiple JDO instances on the application server tier will have
> connections to the same underlying datasource (in this case, RDBMS). I
> am primarily concerned with the problem of keeping caches in sync
> between the different app servers; it can be conveniently assumed that
> no external processes are directly modifying the RDBMS (i.e. not using
> Castor APIs).
>
> Has any additional work been done either to implement a shared cache
> invalidation/mirroring scheme or to further analyze the problem? Has
> anyone implemented their own hacks?
>
> I would be interested in contributing to implement such a mechanism if
> necessary.
>
> Thanks,
>
> Wes
>
> -----------------------------------------------------------
> If you wish to unsubscribe from this mailing, send mail to
> [EMAIL PROTECTED] with a subject of:
> unsubscribe castor-dev
>
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
