Closed Bug 482792 Opened 15 years ago Closed 15 years ago

Provide a wipeClient, wipeRemote, resetService for weave service

Categories

(Cloud Services :: General, defect, P1)

defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: Mardak, Assigned: Mardak)

References

Details

Attachments

(1 file)

For the reset UI, it'll need ways to get rid of all data on the client, on the remote clients. A useful helper resetService would be nice to get rid of non-engine service caches, etc.
Blocks: 468694
Attached patch v1Splinter Review
Refactor out resetService from resetClient (for clearing logs, cache, etc).

Add wipeClient that resets services stuff and calls wipe on each engine (which will call its own reset then wipe data).

Add wipeRemote that just sends the wipeAll command. (Originally I had it wipe the server... but that caused syncIDs to mismatch when resyncing after the wipe which would cause local data to be reset.. including the wipeAll command.)
Assignee: nobody → edilee
Status: NEW → ASSIGNED
Attachment #366900 - Flags: review?(thunder)
Comment on attachment 366900 [details] [diff] [review]
v1

Looks good, except:

>+  /**
>+   * Wipe all remote user data by wiping the server then telling each remote
>+   * client to wipe itself.
>+   *
>+   * @param onComplete
>+   *        Callback when this method completes
>+   */
>+  wipeRemote: function WeaveSvc_wipeRemote(onComplete) {

wipeRemote needs an optional engine list to use instead of sending wipeAll.  Split this to a followup bug if you prefer, though.
Attachment #366900 - Flags: review?(thunder) → review+
http://hg.mozilla.org/labs/weave/rev/72029d49cd62
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Priority: -- → P1
Resolution: --- → FIXED
Blocks: 482898
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.