update/405 question

I am working on a little backup app utilizing sitecopy (great software, 
BTW --- and I use cadaver as well) and I'm running into one final 
little problem.  I'm using WebDAV over HTTPS.

Occasionally, my users will go to perform a backup, which is really 
just a 'sitecopy -uo <site>' after a previous run was cancelled or 
otherwise aborted.  Their local sitecopy status cache will be out of 
sync with the remote version, and when the collection update is 
attempted, the subdirectories on the server will have already been 
created so sitecopy fails with a bunch of 405 Method Not Allowed HTTP 
errors.

Then, sitecopy will exit with errors and throw my app out of whack 
because, well, it exited with errors.  However, if only sitecopy would 
try to do the update without the failed mkdir things would be fine.

My questions is this:

I see in the past (via the archives) that the 405 was changed from a 
409 and that is according to spec.  However, is there a less fatal way 
to handle this situation that could be implemented in sitecopy?  Can't 
sitecopy just see the directories as already existing and then start 
uploading the content?

Thanks for any tips or advice.

-- 
Justin R. Miller
[email protected]

_______________________________________________
sitecopy maillist  -  [email protected]
http://dav.lyra.org/mailman/listinfo/sitecopy