W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > April to June 2002

[w3c-dist-auth] <none>

From: Rajiv A V <rajiv_av@infosys.com>
Date: Tue, 11 Jun 2002 20:33:19 +0530
Message-ID: <1BD922A62552D411B48A00D0B7472375042F732E@kecmsg04.ad.infosys.com>
To: <w3c-dist-auth@w3c.org>
  I have a very trival issue in the use of lock tokens. reading about the use of lock tokens from the RFC it seems that a process (user)should be aware of the resources he is deleting. But let us assume that my client fetches lock tokens (performs lock discovery) on a need basis. Now assume that I want to delete a folder resource inside which I have some stuff that I have locked myself. I have 2 ways to implement it

a) dont delete the resouce since the user hasnt seen the resource yet and wait for the user to see all the resources that he has locked (effectively meaning that then he has a lock token for all the needed resources because thats when the lock discovery is done)
b) when i recieve that detail from the server that tells me that some resouce is locked, just inform the user that there are locks inside        the folder. then on user confirmation the client would interally fetch all the lock tokens for resources that are locked inside the folder and goes ahead with the delete. this would be transparent to the user but the user knows that he is deleting resources that he has a lock on.

I know this is a implementation issue but please let me know which is the right way to do it and would be more webdav compliant.

 thanks and regards,
Received on Tuesday, 11 June 2002 11:02:45 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:25 UTC