[
https://issues.apache.org/jira/browse/JCR-779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12481570
]
Julian Reschke commented on JCR-779:
------------------------------------
I don't think that option 1 is going to work well. It would introduce local
state into the the WebDAV server component, where before there wasn't any.
Furthermore, it will be hard to implement in setups where many WebDAV server
instances talk to the same JCR server (think HTTP-level load balancing).
Furthermore, an existing document store may already support lock timeouts (very
likely if it also supports WebDAV), in which case it would be *much* easier
just to expose that through the JCR API.
> 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.
