[ https://issues.apache.org/jira/browse/JCR-779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12481613 ]
Jukka Zitting commented on JCR-779: ----------------------------------- I like the approach of using the content model for this, and actually I don't think we'd even need any special processing or magic properties to make this happen. Even a standard node type like the following should be enough: [ext:lockable] > mix:lockable mixin - ext:timeout (DATE) ignore We could add a process in Jackrabbit (or in an external client that has some way to retrieve the lock token of a node) that observes such ext:lockable nodes an unlocks them when the timeout has been reached. Refreshing the timeout would require just updating the ext:timeout property. (I'm not sure if there's a chance for some race conditions on locking/unlocking the node and setting the timeout property.) Would that cover the use case, or do we need some more internal mechanism? > Timeout for Session and/or Lock > ------------------------------- > > Key: JCR-779 > URL: https://issues.apache.org/jira/browse/JCR-779 > Project: Jackrabbit > Issue Type: New Feature > Components: locks > Environment: All environments > Reporter: Sridhar > Priority: Minor > > I think there needs to be a mechanism where we can set the timeout for a > particular jcr Session. Or at the most, there should be a provision to set a > timeout for a lock on a node. > Hope this is implemented soon. > Thanks. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.