Closed
Bug 480457
Opened 15 years ago
Closed 15 years ago
Expose a resetClient API for weave service and engines
Categories
(Cloud Services :: General, defect)
Cloud Services
General
Tracking
(Not tracked)
RESOLVED
FIXED
0.3
People
(Reporter: Mardak, Assigned: Mardak)
References
Details
Attachments
(1 file, 1 obsolete file)
|
5.69 KB,
patch
|
hello
:
review+
|
Details | Diff | Splinter Review |
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•15 years ago
|
||
Add resetClient for both weave service and engines.
|
||
Updated•15 years ago
|
Target Milestone: -- → 0.3
|
|
Assignee | |
Comment 2•15 years ago
|
||
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•15 years ago
|
||
Comment on attachment 364479 [details] [diff] [review] v1.1 looks good too.
Attachment #364479 -
Flags: review?(thunder) → review+
|
|
Assignee | |
Comment 4•15 years ago
|
||
http://hg.mozilla.org/labs/weave/rev/2092375a456b
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
|
||
Updated•15 years ago
|
Component: Weave → General
Product: Mozilla Labs → Weave
Version: Trunk → unspecified
|
||
Updated•15 years ago
|
QA Contact: weave → general
You need to log in
before you can comment on or make changes to this bug.
Description
•