Closed Bug 480490 Opened 14 years ago Closed 14 years ago

Expose a wipeServer API for weave service

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)

v1
3.21 KB, patch
hello
: review+
Details | Diff | Splinter Review 
Apparently there used to be a resetServer from long time back.. Not sure what a "reset" server would mean in relation to..

wipeClient, resetClient, wipeServer, resetServer.

We're making "reset" mean get rid of temporary stuff like caches while wipe means get rid of data.

Oh and apparently there's an existing serverWipe, but that's not really a verb.. :p
Attached patch v1 — — Splinter Review 
[].forEach(function() { yield

That causes bad stuff because it makes the callback a generator... :(

I'll switch the clientReset patch in bug 480457 to also use a plain |for each| instead of |forEach|.
Assignee: nobody → edilee
Status: NEW → ASSIGNED
Attachment #364477 - Flags: review?(thunder)
Oh. And I'm glad to report that my weave now works in syncing data :) Yay server wipe.
doh! of course, I forgot about the yield in there!
Attachment #364477 - Flags: review?(thunder) → review+
Comment on attachment 364477 [details] [diff] [review]
v1

looks good.
http://hg.mozilla.org/labs/weave/rev/f8d0e01af27f
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
fixed now!
Target Milestone: -- → 0.3
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.