Push Notifications

Registered by John Lenton on 2013-11-11

Push notifications! Or how you can write an app that polls a service for updates when the app can get stopped at any time by app lifecycle policy. You need to know about this stuff.

Blueprint information

Status:
Not started
Approver:
Thomas Voß
Priority:
Essential
Drafter:
John Lenton
Direction:
Approved
Assignee:
John Lenton
Definition:
Approved
Series goal:
Accepted for trusty
Implementation:
Unknown
Milestone target:
milestone icon ubuntu-14.04

Related branches

Sprints

Whiteboard

We present a proposed first iteration of our Push Notifications API, including four use cases and a somewhat deep drive into some of the implementation details (internal APIs) that might be relevant or of interest to application developers. We'd like to receive comments about these use cases, or other use cases for the service, especially where aspects of the use case is not met.

(?)

Work Items

Work items for ubuntu-13.12:
[lucio.torre] Simple server: TODO

Work items for ubuntu-14.01:
[chipaca] Simple client-side daemon: TODO
define dbus api: TODO
get first running version of the service: TODO
enable opening of the connections: TODO
enable receiving a notification from a/the server: TODO
[lucio.torre] Simple server in prodstack: TODO
QT: TODO
Desing QML API: TODO
QML: TODO
SDK: TODO

Work items for ubuntu-14.03:
[chipaca] Message interception: TODO
[chipaca] Urgency (client-side): TODO
[lucio.torre] Urgency (server-side & protocol): TODO
[lucio.torre] Bundling: TODO

Work items for ubuntu-14.04:
[lucio.torre] scalable, persistent, etc: TODO

Dependency tree

* Blueprints in grey have been implemented.