jackrabbit-dev mailing list archives

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

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

Julian Reschke commented on JCR-779:

I feared you would ask .-)

For lock timeout, we would

- need the ability to specifiy it upon lock creation (or set it afterwards)
- need to reset the lock timeout
- discover the current value

If we don't want to change the Java API, we could just have a mixin node type that defines
the timeout information, and make that writeable, such as:

ext:lockable extends mix:lockable

  - ext:lockRefreshed (date)  ignore
  - ext:lockTimeoutSeconds (long)  ignore

Setting ext:lockRefreshed would refresh the lock.ext:lockTimeoutSeconds would used to compute
when the lock times out.

For WebDAV, we IMHO also would need one additional property to persist the lock owner information
(see <http://greenbytes.de/tech/webdav/draft-ietf-webdav-rfc2518bis-18.html#owner>).

> 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