On Fri, Jun 24, 2005 at 02:16:35PM -0400, Haber, Orna wrote:
> The purpose behind the locking need is to avoid situation where more
> than one client is try to modify the same file (at the same time).
> Because of the file (sensitive) contents, it is important to wait until
> one client finish updating the file before another client starts
> updating it.
> What is the best way to provide this locking (since curl is not the
> answer)?

How are you doing the file upload? DAVS ought to handle locking issues
itself. With a POST script, you could use whatever OS file locking services
are available to create an OS-level lock on the file (e.g. flock or fcntl
on *NIX). There are too many variables to know what's best in your
situation, and you haven't given many details.

>>> Dan

-- 
http://www.MoveAnnouncer.com              The web change of address service
          Let webmasters know that your web site has moved