I am facing a similiar situation. To my disappointment, the
LockMethod.TIMEOUT_INFINITY doesn't work as I expect it to. I would expect
the Lock to *never* expire, yet it does. Does anyone have any information
regarding this? I am using Apache 1.3.x with mod_dav 1.0.2 as my server.
For my case, constantly renewing the lock is not an option.
Thanks
Brian Olore
[EMAIL PROTECTED]
Russ
<[EMAIL PROTECTED]> To: Slide Users Mailing List
<[EMAIL PROTECTED]>
cc:
06/04/2002 02:37 Subject: Re: How to achieve
non-expiring lock?
AM
Please respond to
"Slide Users
Mailing List"
I see, so it seems that after setting a big value for expiration I will
need to write extra code to renew the lock. Thanks.
Stephan Michels wrote:
>On Tue, 4 Jun 2002, Russ wrote:
>
>
>
>>Hi,
>> I guess the subject says everything.
>>
>> I am using Slide API directly and NodeLock's constructor requires an
>>expiry date parameter for locking a resource. What value do I need to
>>pass in to get a non-expiring lock? Or must I explicitly code to renew
>>the lock automatically on expiry?
>>
>>
>
>Take a look into LockMethod.java from the WebDAV server.
>
> // Resource type
> revisionDescriptor.setResourceType("<lock-null/>");
>
> // Creating the revision descriptor
> content.create(slideToken, lockInfo_lockSubject,
> revisionDescriptor, null);
>
> // HACK
> // Setting a max timeout when creating a lock-null
> // resource because the associated lock-null wouldn't
> // be automatically removed when the lock expires
> lockDate = new Date((new Date()).getTime()
> + (MAX_TIMEOUT * 1000));
>
>It seems that you have to set the resource type, and very big value for
>the lock date.
>
>Stephan Michels.
>
>
>--
>To unsubscribe, e-mail: <
mailto:[EMAIL PROTECTED]>
>For additional commands, e-mail: <
mailto:[EMAIL PROTECTED]>
>
>
>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
