Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Message-ID: <9689808.1174044309865.JavaMail.jira@brutus>
Date: Fri, 16 Mar 2007 04:25:09 -0700 (PDT)
From: "Jukka Zitting (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Subject: [jira] Commented: (JCR-779) Timeout for Session and/or Lock
In-Reply-To: <6901879.1173352584392.JavaMail.root@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jukka Zitting commented on JCR-779:
-----------------------------------

Hmm, good points. What would the JCR API extension look like?

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