Closed Bug 480457 Opened 14 years ago Closed 14 years ago

Expose a resetClient API for weave service and engines

Categories

(Cloud Services :: General, defect)

Product:
Cloud Services
Component:
General
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: Mardak, Assigned: Mardak)

References

Details

Attachments

(1 file, 1 obsolete file)

v1.1
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
Attached patch v1 (obsolete) — — Splinter Review 
Add resetClient for both weave service and engines.
Target Milestone: -- → 0.3
Attached patch v1.1 — — Splinter Review 
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 on attachment 364479 [details] [diff] [review]
v1.1

looks good too.
Attachment #364479 - Flags: review?(thunder) → review+
http://hg.mozilla.org/labs/weave/rev/2092375a456b
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
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.