Expose a resetClient API for weave service and engines

RESOLVED FIXED in 0.3

Status

Cloud Services
General
RESOLVED FIXED
9 years ago
8 years ago

People

(Reporter: Mardak, Assigned: Mardak)

Tracking

unspecified
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment, 1 obsolete attachment)

resetClient is not as destructive as wipeClient in that resetClient only drops meta data like lastSync time. wipeClient will be reserved for getting rid of stuff locally on the client.

E.g., tabs: reset = drop meta data file; wipe = close all tabs
(Assignee)

Comment 1

9 years ago
Created attachment 364441 [details] [diff] [review]
v1

Add resetClient for both weave service and engines.

Updated

9 years ago
Target Milestone: -- → 0.3
(Assignee)

Comment 2

9 years ago
Created attachment 364479 [details] [diff] [review]
v1.1

Convert resetClient to async which will also call each engine async.... I suppose it isn't possible to run each engine's resetClient in parallel in js right now.. ?
Attachment #364441 - Attachment is obsolete: true
Attachment #364479 - Flags: review?(thunder)

Comment 3

9 years ago
Comment on attachment 364479 [details] [diff] [review]
v1.1

looks good too.
Attachment #364479 - Flags: review?(thunder) → review+
(Assignee)

Comment 4

9 years ago
http://hg.mozilla.org/labs/weave/rev/2092375a456b
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → FIXED

Updated

8 years ago
Component: Weave → General
Product: Mozilla Labs → Weave
Version: Trunk → unspecified
QA Contact: weave → general
You need to log in before you can comment on or make changes to this bug.