Yes, it does. Both parts are pertained.
The command line client, to handle the commands and options coming from the line 
and client library to handle the webdav methods in the right way (correction of 
webdavResource.unlockMethod).

Regards
Thomas

-----Urspr�ngliche Nachricht-----
Von: Michael Oliver [mailto:[EMAIL PROTECTED] 
Gesendet: Mittwoch, 12. Mai 2004 16:31
An: 'Slide Users Mailing List'
Betreff: RE: Problem with unlock on command line client

Does this patch also pertain to the client library or just the command line client?  I 
also tried a JUnit test of the webdavResource.unlockMethod and it too failed.

Michael Oliver
CTO
Matrix Intermedia Inc.
3325 N. Nellis Blvd, #1
Las Vegas, NV 89115
Phone:(702)643-7425
Fax:(520)844-1036
 

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

*       
        setting timeout for locks
*       
        setting different owner of lock (important for testing)
*       
        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.
 
best regards
Thomas
 
 
 
________________________________

Thomas Bernert
C:1 Financial Services GmbH
Dorotheenstra�e 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

 
________________________________

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

 

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.

 

Then looking at the browser connected to same server I see under 319.doc

 

Locks Info

Subject

Type

Expiration

Inheritable

Exclusive

/users/root

/actions/write

Tue, 11 May 2004 09:18:45 MST

true

true

 

All is well

 

But then in the same session I do 

 

unlock 319.doc

Unlocking '/slide/files/matrix/319.doc':failed.

OK (200) opaquelocktoken:2786d7fa0aa2f1de9904ca8d30fafaad

 

And the browser doesn't change showing same 

 

Locks Info

Subject

Type

Expiration

Inheritable

Exclusive

/users/root

/actions/write

Tue, 11 May 2004 09:18:45 MST

true

true

 

 

Questions:

 

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?

 

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?

 

__________________________________________________________________
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:  



*  More ways to contact me <http://wwp.icq.com/318986322> 
__________________________________________________________________

 



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

Reply via email to