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
Created attachment 364441 [details] [diff] [review] v1 Add resetClient for both weave service and engines.
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.. ?
Comment on attachment 364479 [details] [diff] [review] v1.1 looks good too.
Attachment #364479 - Flags: review?(thunder) → review+
Status: NEW → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → FIXED
Component: Weave → General
Product: Mozilla Labs → Weave
Version: Trunk → unspecified
You need to log in before you can comment on or make changes to this bug.