Have a look at: http://greenbytes.de/tech/webdav/rfc3253.html#PROPERTY_auto-version
/jacob
----- Original Message ----- From: "Tim Frank" <[EMAIL PROTECTED]>
To: "Slide Users Mailing List" <[EMAIL PROTECTED]>
Sent: Thursday, November 25, 2004 3:33 PM
Subject: Re: the question about checkout and lock
Yong,
I did some experimenting with this a while ago to get na understanding of how checkout/checkin and locking works. Checkout/checkin work independently of locks to some degree. Meaning you can checkout without locking so any user with access to the resource could modify it or perform checkin/uncheckout operations.
If you decide to put a lock on a checkedout file, then there are various parts of the spec that dictate that when the lock is removed it is AUTOMATICALLY checked in. This is for interoperability with "dumb" webdav clients.
I believe I tested the scenario when I could checkout a file, lock/unlock it as many times as I wanted, then checkin when I wanted. The specification does not enforce locking upon checkout. The use is up to the end-user application.
Tim
Yong Hu wrote on 25/11/04 03:57 AM:All,
Who could give me a clear explain the checkout and lock in Slide?
I don't use lockMethod currently, but I use checkoutMethod/checkinMethod to implement the versioncontrol.
I find that if user1 checkout one file, another user can do uncheckout or checkin on this file. I wonder why not the lock is added to one file after it is checked out in order that other user can't operate on it?
Regards Yong
--------------------------------- Do You Yahoo!? 嫌邮箱太小？雅虎电邮自助扩容！
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
