[
https://issues.apache.org/jira/browse/OAK-960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13748462#comment-13748462
]
Chetan Mehrotra commented on OAK-960:
-------------------------------------
That should work!! I was storing something similar to saveCount in threadlocal
map which can be saved as an instance variable. Hence we only incur the cost of
adding one integer to Threadlocal map.
So we can do away with interceptor. Just that I wanted to use the same
interceptor to try a scenario where instead of maintaining a thread local map I
would maintain the state in a global variable effectively causing automatic
session refresh for all session bringing it at par with JR2. But may be we do
not want to do that!!
btw you would still provide me a way for logging interception :)
> Provide an interceptor for SessionOperations
> --------------------------------------------
>
> Key: OAK-960
> URL: https://issues.apache.org/jira/browse/OAK-960
> Project: Jackrabbit Oak
> Issue Type: New Feature
> Components: core, jcr
> Affects Versions: 0.8
> Reporter: Chetan Mehrotra
> Assignee: Chetan Mehrotra
> Priority: Minor
> Attachments: OAK-960.patch
>
>
> To support certain scenarios like
> * Logging session operation being performed
> * Coordinating refresh state among multiple session used in same thread
> It would be helpful to expose a {{SessionOperationInterceptor}} which can be
> invoked by the {{SessionDelegate}} before and after the operation is
> performed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
