Closed
Bug 805686
Opened 13 years ago
Closed 10 years ago
workerapi heartbeat and error recovery
Categories
(Firefox Graveyard :: SocialAPI, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: mixedpuppy, Unassigned)
References
Details
(Whiteboard: [needs-api-change])
We should have a heartbeat message from chrome to the worker that the worker must respond to. We also probably need to implement this prior to facebook. proposal:
- if first heartbeat fails, immediate error ui.
- if heartbeat later fails, reload, new heartbeat response means it works again
- if x reloads in x time, unload show error ui.
- social.initialize should pass an api version
- social.initialize-response should come back with a supported version number
- for now, heartbeat would only become functional if the response is our initial api version or greater.
Reporter | ||
Updated•13 years ago
|
Whiteboard: [Fx17]
Updated•13 years ago
|
Whiteboard: [Fx17]
Comment 1•13 years ago
|
||
Sorry for the bug-spam. This is a first cut at bugs that need (or potentially need) a change to the social api to be implemented appropriately.
Whiteboard: [needs-api-change]
Reporter | ||
Comment 2•10 years ago
|
||
preferably we move to service workers, wontfix'ing this.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
Updated•6 years ago
|
Product: Firefox → Firefox Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•