Client never deletes old history data

RESOLVED FIXED in 0.3

Status

P2
normal
RESOLVED FIXED
10 years ago
10 years ago

People

(Reporter: hello, Unassigned)

Tracking

unspecified
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

10 years ago
The client should send a DELETE to the server to delete old data regularly.
(Reporter)

Updated

10 years ago
Blocks: 468683
Target Milestone: -- → 0.3
(Reporter)

Comment 1

10 years ago
Would really like this for 0.3.

Note that currently we wipe all data on version upgrades, and that's why this is not a P1.
Priority: -- → P2
(Reporter)

Updated

10 years ago
Duplicate of this bug: 478062

Comment 3

10 years ago
Server history and client local history have different meaning.
Somewhere should be separete settings of a server trail properties. 
For public services it should be server-side hard limits.
For private servers limits can be client-depended.

There shouldn't be a situation, where purging of client history cleans all server history. Only "clear server data" or special "server housekeeping" should clean server history.

In real life often uses limits "by size in KB", "by record count", "by age", in many combinations, with upper limits, and guaranteed spaces. 
If a "reference" server will newer propose this functionality, it should not disable this possibilities at all.

One of possible variants to make housekeeping on server side - replace old record with new if record count limit touched... For example, remove 10% of old records, when user tries to add 100%th record.
(Reporter)

Comment 4

10 years ago
(In reply to comment #3)
> For public services it should be server-side hard limits.
> For private servers limits can be client-depended.

This bug is to implement the bare minimum required--simply to delete old records based on some hardcoded criteria.  But, it would be nice if it was configurable, sure.
 
> One of possible variants to make housekeeping on server side - replace old
> record with new if record count limit touched... For example, remove 10% of old
> records, when user tries to add 100%th record.

I agree that some of this work could/should be done server-side.  We should explore that possibility in future iterations of the client/server.
(Reporter)

Comment 5

10 years ago
Fixed:

http://hg.mozilla.org/labs/weave/rev/f96f8c54b053
Status: NEW → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → FIXED
Component: Weave → General
Product: Mozilla Labs → Weave
QA Contact: weave → general
You need to log in before you can comment on or make changes to this bug.