jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "angela (JIRA)" <j...@apache.org>
Subject [jira] Updated: (JCR-779) Timeout for Session and/or Lock
Date Fri, 16 Mar 2007 10:51:09 GMT

     [ https://issues.apache.org/jira/browse/JCR-779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

angela updated JCR-779:

    Component/s:     (was: webdav)

i don't agree, that this is a WebDAV issue...

as i said in the mailing list its not the responsibility of a dav-server to determine whether
a lock present on a node might still be used or if it can be removed. the webdav implementation
represents a dav-server on top of a jsr 170 repository present and not on top of jackrabbit.
and according to the specification it's up to the jsr 170 implementation if locks can timeout
and when they timeout. therefore i don't think the dav-server should deal with this.

removing webdav component again.

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

View raw message