[jboss-jira] [JBoss JIRA] Updated: (JBCACHE-957) Allow per-node configuration of LockParentForChildInsertRemove

Wed Oct 10 11:54:05 EDT 2007

     [ http://jira.jboss.com/jira/browse/JBCACHE-957?page=all ]

Manik Surtani updated JBCACHE-957:
----------------------------------

    Fix Version/s: 2.1.0.BETA1

> Allow per-node configuration of LockParentForChildInsertRemove
> --------------------------------------------------------------
>
>                 Key: JBCACHE-957
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-957
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.GA, 1.4.1.SP1
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>             Fix For: 2.1.0.GA, 2.1.0.BETA1
>
>         Attachments: lock.diff
>
>
> Use the new LockParentForChildInsertRemove as a global default that sets a per-node behavior.  Expose an API in Node (not NodeSPI) that allows the application to change the behavior for an individual node.
> Use case: session replication, which stores data in a structure like this:
> /SESSION/webapp/session1/.../...
> /SESSION/webapp/session2/.../...
> The session managment layer wants the greater correctness that comes with enforcing LockParentForChildInsertRemove="true" with the sessionX node and below.  But requiring a WL on /SESSION/webapp before any session could be added or removed will greatly disrupt session creation and expiration.  This feature allows the best of both worlds, by allowing the application to set LockParentForChildInsertRemove="false" on /SESSION and /SESSION/webapp.
> This is a simple alternative to lock striping in the node's children map.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira