Re: [platform-vcm-dev] Team provider problems with replacing files

[Geoffrey M Clemm <geoffrey.clemm@xxxxxxxxxx>]

Most of the reliability benefits can be achieved by
doing a "copy-to-temp",
"update", "remove-temp" sequence,
which does not break the semantics of "update".

Cheers,
Geoff

Jim wrote on 09/16/2003 09:59:30 AM:
> 
> A complicating factor in a drag and drop situation is how to handle
a
> failure. An update in place (replace) is destructive. If the operation
> fails to complete, the original file is lost. A copy, delete, and
rename is
> a safer implementation. Unfortunately, this creates a complication
and
> dilemma for repository providers. The situation is not limited to
eclipse
> drag and drop. Any plug-in might implement a file replace operation
via
> delete and add (and they do).