Closed
Bug 482672
Opened 17 years ago
Closed 16 years ago
server updates mtime on depth/index-only updates
Categories
(Cloud Services Graveyard :: Server: Sync, defect, P2)
Cloud Services Graveyard
Server: Sync
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: hello, Unassigned)
References
Details
I have not verified this independently of the add-on, but it looks like updates like this (in a POST to a collection):
{"id":"{8a5651d2-036a-bd4d-81b6-6fc7e1eff4da}607","depth":1,"sortindex":106}
are causing another client to receive updates for that item as if it had been modified.
|
Reporter | |
Comment 1•17 years ago
|
||
Would be nice to get this in for 0.3.
|
|
Reporter | |
Comment 2•17 years ago
|
||
Fixing component. Would still like this for 0.3, as it causes a bunch of extra churn on the client.
Component: Weave → Weave Server
QA Contact: weave → weaveserver
|
||
Updated•17 years ago
|
Target Milestone: 0.3 → 0.4
|
|
||
Updated•16 years ago
|
Component: Weave Server → Server
Product: Mozilla Labs → Weave
Target Milestone: 0.4 → ---
|
||
Updated•16 years ago
|
QA Contact: weaveserver → server
|
|
||
Comment 3•16 years ago
|
||
No more depth/index updates with 0.5
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → INVALID
|
||
Updated•3 years ago
|
Product: Cloud Services → Cloud Services Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•