On Thu, Mar 07, 2002 at 02:32:47PM -0700, Jeffrey P Shell wrote:
> A WebDAV client may request a timeout length for a lock, but it's basically
> just a suggestion.  You say you investigated again "some time later".
> Zope's default timeout is thirty minutes.  Clients can ask for longer ones
> and Zope will obey, but the 30 minutes is granted for 'infinite' timeout
> requests (the spec says that the server may decide the timeout time
> independent of the clients request).  The timeout should get refreshed with
> every HTTP request made by you (the lock owner).  But the timeout also
> exists so that the problem of "Person X locks a document for editing, and
> then leaves in a hurry (forgetting to release his lock).  Person Y really
> needs to edit the document, but it's held hostage by X's lock".
> 
> Cadaver may be caching the locks.  Since HTTP/WebDAV are stateless, you have
> to refresh your listing in order to see if locks are still there.  Most GUI
> based WebDAV clients have a "refresh listing" option, which is the only way
> they can know of new members in a collection and new lock states.

Thanks for the informations, I'll try to restest more carefully in the
light of your message.

bye,

Jerome Alet

_______________________________________________
Zope-Dev maillist  -  [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://lists.zope.org/mailman/listinfo/zope-announce
 http://lists.zope.org/mailman/listinfo/zope )

Reply via email to