document box.com rename problem
This commit is contained in:
parent
2ca1d3cc01
commit
7f8892f2d2
1 changed files with 6 additions and 0 deletions
|
@ -41,3 +41,9 @@ Low priority:
|
||||||
Run each pair in turn. Then run the current rename code. Although this
|
Run each pair in turn. Then run the current rename code. Although this
|
||||||
still probably misses cases, where eg, content cycles amoung 3 files, and
|
still probably misses cases, where eg, content cycles amoung 3 files, and
|
||||||
the same content amoung 3 other files. Is there a general algorythm?
|
the same content amoung 3 other files. Is there a general algorythm?
|
||||||
|
* Exporting to box.com via webdav, a rename of a file behaves
|
||||||
|
oddly. The rename to the temp file succeeds, but the rename of the temp
|
||||||
|
file to the final name fails.
|
||||||
|
Hypothesis: Those are done in separate http connections and it might be
|
||||||
|
talking to two different backend servers that are out of sync.
|
||||||
|
So, making export cache connections might help.
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue