Closed Bug 1261193 Opened 9 years ago Closed 9 years ago

Prototype Firebase database connection

Categories

(Hello (Loop) :: Client, defect)

Product:
Hello (Loop)
Component:
Client
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: ianbicking, Assigned: ianbicking)

References

Details

User Story

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
And: https://developer.mozilla.org/en-US/docs/Web/API/Server-sent_events/Using_server-sent_events

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.
No description provided.
Blocks: akita-planning
User Story: (updated)
User Story: (updated)
I'll be prototyping here: https://github.com/ianb/firebase-client-prototype
Assignee: nobody → ianb
I did some prototyping with the "super flat" structure to get streaming updates without getting everything that exists. I think we've done enough prototyping and actual implementation happens under bug 1274165.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.