ExtendedStore allows you to invalidate entries. Subclass it and add your
code that talks to your client store to find out which entries to
delete. Use something like getTxCache().remove(null, [key to be
invalidated] on objectsCache, permissionsCache, etc.
Oliver
Carlos Villegas wrote:
Hi,
Daniel Florey wrote:
If LDAP provides some notification mechanism for informing slide about
user/role updates additional user/role caching would be possible to
achieve better performance.
I have a custom store that gets user/role info from an external source.
I set it up in the Domain.xml and it's working but Slide caches the
objects and do not go to my store to get updated info. I can also detect
external updates, but how do I control the caching in Slide? I don't
want to disable caching completely. Is there a way to invalidate a cache
entry from within my store code?
Thanks,
Carlos
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
