Closed
Bug 1261189
Opened 9 years ago
Closed 9 years ago
(bug filed incorrectly)
Categories
(Hello (Loop) :: Client, defect)
Hello (Loop)
Client
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: ianbicking, Unassigned)
Details
Given the licensing of the Firebase SDK, we need to progress with a client of our own making.
This client would make use of the Firebase REST interface: https://www.firebase.com/docs/rest/api/
To be notified of updates it use the streaming API: https://www.firebase.com/blog/2014-03-24-streaming-for-firebase-rest-api.html
See also: https://www.firebase.com/docs/rest/api/#section-streaming
We'll have to account for receiving updates that were generated locally. We'll also have to consider missed updates in the case of a stream disconnect. We can adapt the form of the data we put into Firebase to accommodate our needs.
|
Reporter | |
Updated•9 years ago
|
Blocks: akita-planning
|
|
Reporter | |
Comment 1•9 years ago
|
||
First bug and I already messed up the User Story process :( Redone in Bug 1261193
No longer blocks: akita-planning
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INVALID
Summary: Prototype Firebase database connection → (bug filed incorrectly)
You need to log in
before you can comment on or make changes to this bug.
Description
•