Such a problem should be simple to debug if you post a trace captured with a tool like tcpmon (or however it is called).
Ingo > Thomas, > > I just built a new command line client from HEAD (and patched the > build.xml to do it) and lock/unlock is still failing, I will be entering > a bug shortly. > > I used the simplest case as follows > > [ Slide ] $ connect http://myhost.com:8888/slide (beta1) > - No credentials available for the 'Slide DAV Server' authentication > realm at myhost.com > UserName: root > Password: root > [myhost.com] /slide/ $ cd files > [myhost.com] /slide/files $ ls > Matrix AJCSData > [myhost.com] /slide/files $ cd Matrix > [myhost.com] /slide/files/Matrix $ ls > 319.doc > [myhost.com] /slide/files/Matrix $ locks 319.doc > No locks on /slide/files/Matrix/319.doc > [myhost.com] /slide/files/Matrix $ lock 319.doc > Locking '/slide/files/Matrix/319.doc': succeeded. > [myhost.com] /slide/files/Matrix $ locks 319.doc > Locks for /slide/files/Matrix/319.doc: > ------------------------------------------------ > Exclusive write lock > depth: infinity > owner: root > timeout: 112 > token: opaquelocktoken:asdfjkl45jkl32poi12345678 > [myhost.com] /slide/files/Matrix $ unlock 319.doc > Unlocking '/slide/files/Matrix/319.doc': failed. > OK (200)opaquelocktoken:asdfjkl45jkl32poi12345678 > [myhost.com] /slide/files/Matrix $ locks 319.doc > Locks for /slide/files/Matrix/319.doc: > ------------------------------------------------ > Exclusive write lock > depth: infinity > owner: root > timeout: 20 > token: opaquelocktoken:asdfjkl45jkl32poi12345678 > > > This instance of slide (Beta1) works perfectly with Microsoft Office > products, XP Web Folders as well as WebDrive to lock and unlock the > files so I don't believe it is a server bug. > > > Michael Oliver > CTO > Matrix Intermedia Inc. > 3325 N. Nellis Blvd, #1 > Las Vegas, NV 89115 > Phone:(702)643-7425 > Fax:(520)844-1036 > =20 > > -----Original Message----- > From: Bernert, Thomas [mailto:[EMAIL PROTECTED] > Sent: Wednesday, May 12, 2004 12:17 AM > To: Slide Users Mailing List > Subject: AW: Problem with unlock on command line client > > Hi Michael, > you are rigth. The lock/unlock problems are fixed. The bugfix provides > following functionality : > > *=09 > setting timeout for locks > *=09 > setting different owner of lock (important for testing) > *=09 > setting of lock type (shared or exclusive) > > The patch isn't available for release 2.0. > If you need this patch, get the client from HEAD branch of cvs. > =20 > best regards > Thomas > =20 > =20 > =20 > ________________________________ > > Thomas Bernert > C:1 Financial Services GmbH =20 > Dorotheenstra=DFe 64 > 22301 Hamburg > www.c1-fse.de > email [EMAIL PROTECTED] > Tel +49 40 69213-192 // +49 173 244 94 94 > Fax +49 40 69213-199 > > =20 > ________________________________ > > Von: Michael Oliver [mailto:[EMAIL PROTECTED] > Gesendet: Dienstag, 11. Mai 2004 18:34 > An: Slide Users Mailing List > Betreff: Problem with unlock on command line client > > > > If I use the command line client (2.0beta1) as follows > > =20 > > connect http://myhost.com:8888/slide (also 2.0beta1) > > UserName:root > > Password:****** > > cd files > > cd matrix > > ls > > 319.doc > > lock 319.doc > > Locking '/slide/files/matrix/319.doc': succeeded. > > =20 > > Then looking at the browser connected to same server I see under 319.doc > > =20 > > Locks Info > > Subject > > Type > > Expiration > > Inheritable > > Exclusive > > /users/root > > /actions/write > > Tue, 11 May 2004 09:18:45 MST > > true > > true > > =20 > > All is well > > =20 > > But then in the same session I do=20 > > =20 > > unlock 319.doc > > Unlocking '/slide/files/matrix/319.doc':failed. > > OK (200) opaquelocktoken:2786d7fa0aa2f1de9904ca8d30fafaad > > =20 > > And the browser doesn't change showing same=20 > > =20 > > Locks Info > > Subject > > Type > > Expiration > > Inheritable > > Exclusive > > /users/root > > /actions/write > > Tue, 11 May 2004 09:18:45 MST > > true > > true > > =20 > > =20 > > Questions: > > =20 > > Shouldn't 'lock 319.doc' lock the file with a permanent lock with a > timeout greater than two minutes? > > Is there a property on the server that controls the default lock > timeout? > > =20 > > Shouldn't 'unlock 319.doc' unlock the file in the same session, i.e. > isn't the lock token stored in the client's session? > > =20 > > __________________________________________________________________ > Michael Oliver > > CTO > > Matrix Intermedia Inc > > 3325 N. Nellis Blvd, #1 > > Las Vegas, NV 89115 > > Phone:+1 (702)643-7425 > > Fax +1 (520) 844-1036 > ICQ#: 318986322 > > Current ICQ status: =20 > > > > * More ways to contact me <http://wwp.icq.com/318986322>=20 > __________________________________________________________________ > > =20 > > > > --------------------------------------------------------------------- > 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]
