[jboss-jira] [JBoss JIRA] Updated: (JBCACHE-811) Use InvocationContext to avoid multiple searches for a node

Manik Surtani (JIRA) jira-events at lists.jboss.org
Mon May 19 05:58:27 EDT 2008


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

Manik Surtani updated JBCACHE-811:
----------------------------------

    Fix Version/s: 3.0.0
                       (was: 2.2.0.GA)

Moving this to 3.0.0, as this is where it will really be needed with MVCC.

> Use InvocationContext to avoid multiple searches for a node
> -----------------------------------------------------------
>
>                 Key: JBCACHE-811
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-811
>             Project: JBoss Cache
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Brian Stansberry
>         Assigned To: Manik Surtani
>             Fix For: 3.0.0
>
>
> When an interceptor finds a node, why not throw it in the InvocationContext or something similar and pass it through the stack that way? Subsequent calls to find the node can check the context first before walking the cache tree. Saves redundant walking of the tree.
> We'd need to think very carefully about this, as it exposes 2 paths to access a node -- from a thread's context and from the tree.  Need to ensure concurrent threads always access the same node object for a given Fqn.
> (Side thought -- perhaps disable this for weak isolation levels where the locking behavior in the interceptors make it possible to end up w/ 2 concurrent nodes for the same Fqn).

-- 
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

        



More information about the jboss-jira mailing list