write lock

[robertointernet]

Hi all

I have a scenario where the following happens:

1) I have 400 objects store in jboss-cache that are constantly being updated

2) each object is located in it's own Fqn. So object1 will be in /1/object1, object2 will be in /2/object2, etc

3) there is gui that is being periodically updated with information on the 400 objects

so my question is: when I'm refreshing the gui I don't want to wait until all 400 objects have released their write locks as I don't mind having inconsistent information (user can always click on the object with a readlock to get more detailed information), is this possible using treecache? if yes how?

thanks
Roberto

[ben.wang]

You can use different isolation level such as READ_UNCOMMITTED. But it does not prevent dirty read though.

-Ben

[belaban]

This is currently not really possible (unless you are willing to use READ_UNCOMMITTED).
This is on the roadmap though, in issue http://jira.jboss.com/jira/browse/JBCACHE-106. Here, you will be able to selectively override the method call, e.g. to not acquire any locks

[robertointernet]

Would using treecacheaop make any difference? Can the lock only be applied to the attribute of the object we're actually modifying? Or is the lock always applied to the whole node where the object is located?

thanks for the quick replies
Roberto

[ben.wang]

Lock is orthognal to cacheaop, per se. So it is still applied in the node level.

-Ben