Discussions related to
http://jira.jboss.com/jira/browse/JBCACHE-957 -- Allow per-node
configuration of LockParentForChildInsertRemove.
Elias Ross had a good suggestion on this:
anonymous wrote :
| The Node itself keeps a NodeLock instance. Perhaps the specific choice of lock
(read-write) could be delegated to the NodeLock itself?
|
| In particular, for the method:
|
| boolean acquire(Object caller, long timeout, NodeLock.LockType lock_type);
|
| it might make sense to replace the LockType parameter with an operation parameter?
E.g.
|
| boolean acquire(Object caller, long timeout, NodeLock.Operation op);
|
| Then there needs to be some way to set the particular strategy per node. It's
theoretically possible, but there needs to be a standard API to expose this. E.g.
|
| void setLockStrategy( ... );
|
| With this in mind, the NodeLock interface should get revisited in time for 2.0.
|
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4008104#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...