Last Comment Bug 480457 - Expose a resetClient API for weave service and engines
: Expose a resetClient API for weave service and engines
Product: Cloud Services
Classification: Client Software
Component: General (show other bugs)
: unspecified
: All All
-- normal (vote)
: 0.3
Assigned To: Ed Lee :Mardak
Depends on:
Blocks: 480057 480448
  Show dependency treegraph
Reported: 2009-02-26 17:17 PST by Ed Lee :Mardak
Modified: 2009-06-15 19:35 PDT (History)
1 user (show)
See Also:
Crash Signature:
QA Whiteboard:
Iteration: ---
Points: ---

v1 (5.04 KB, patch)
2009-02-26 17:41 PST, Ed Lee :Mardak
no flags Details | Diff | Splinter Review
v1.1 (5.69 KB, patch)
2009-02-26 22:36 PST, Ed Lee :Mardak
thunder: review+
Details | Diff | Splinter Review

Description User image Ed Lee :Mardak 2009-02-26 17:17:05 PST
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
Comment 1 User image Ed Lee :Mardak 2009-02-26 17:41:21 PST
Created attachment 364441 [details] [diff] [review]

Add resetClient for both weave service and engines.
Comment 2 User image Ed Lee :Mardak 2009-02-26 22:36:30 PST
Created attachment 364479 [details] [diff] [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.. ?
Comment 3 User image Dan Mills [:thunder] 2009-02-28 23:26:12 PST
Comment on attachment 364479 [details] [diff] [review]

looks good too.
Comment 4 User image Ed Lee :Mardak 2009-03-03 16:24:34 PST

Note You need to log in before you can comment on or make changes to this bug.