Bug #1466
No way to detect a server delete
| Status: | Closed | Start date: | 10/10/2011 | |
|---|---|---|---|---|
| Priority: | Medium | Due date: | ||
| Assignee: | Panagiotis Kanavos | % Done: | 100% |
|
| Category: | Core | Spent time: | - | |
| Target version: | Alpha |
Description
The If-Modified-Since tag will not return deletes. A full listing will return all existing objects but we will have no way to detect which files were deleted and which just haven't been uploaded yet
Could we find the deleted files from a history list?
Associated revisions
Added notification messages for conflicts and multifile operations on Pithos.Core/PithosMonitor.cs
Added simple status display for conflict and multifile operations in ShellViewModel.cs
Added Conflict file status
Modified NetworkAgent.cs to mark local-only files as "in conflict" during the first poll and delete any non-conflict local-only files on subsequent runs. Closes #1466, #1931
History
#1 Updated by Panagiotis Kanavos over 12 years ago
When a file state exists but no cloud file is encountered in a full listing, the file should be considered deleted.
Q: How to detect without forcing a full listing?
#2 Updated by Panagiotis Kanavos over 12 years ago
- Category set to Core
- Assignee set to Panagiotis Kanavos
#3 Updated by Panagiotis Kanavos over 12 years ago
- Target version set to Alpha
#4 Updated by Panagiotis Kanavos over 12 years ago
- Status changed from New to Resolved
Instead of trying to detect a delete, the first time the client runs we mark all local files not found on the server as "In Conflict" and let the user decide.
On subsequent polls, we delete any missing files, except those in conflict.
#5 Updated by Panagiotis Kanavos about 12 years ago
- Status changed from Resolved to Closed
- % Done changed from 0 to 100
Applied in changeset 9c6d31931196c90864d509843bfac0e62dc965bc.