[ https://issues.apache.org/jira/browse/JCR-779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12481567 ]
Jukka Zitting commented on JCR-779: ----------------------------------- There are basically two ways to implement proper support for the Timeout header in a LOCK request based on just the JCR API: 1) Keep track of opened locks and their timeout values in the WebDAV server, explicitly unlocking them when the timeout is reached. 2) Implement lock timeouts in jackrabbit-core, and use the custom API extension to access that functionality in the WebDAV server. Option 1 is localized to the WebDAV implementation, requires no JCR API extensions, and will work with all JCR implementations that support locking. I think it's by far a better solution to this issue. > 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.