259
edits
CloudServices/Notifications/Push/Arch: Difference between revisions
CloudServices/Notifications/Push/Arch (view source)
Revision as of 00:08, 6 April 2012
, 6 April 2012no edit summary
(Created page with "== What the Client Does == # Log in to Firefox with BrowserID. # Start Notifications client. # Authenticate with Push Notification Service. # Sync push URLs. # Get stored message...") |
No edit summary |
||
| Line 42: | Line 42: | ||
* Accept messages from third-party sites | * Accept messages from third-party sites | ||
* Pass messages to routing layer | * Pass messages to routing layer | ||
=== Routing Layer === | |||
When a messages comes in through the API it needs to be routed to the correct | |||
socket server(s) to get pushed to a client. There may be zero, one, or many | |||
connected clients. Routing possibilities: | |||
* Registry server that tracks which socket server(s) a client is connected to, and then: | |||
** direct RPC to the socket server | |||
** pub/sub to a channel for that server | |||
* Open pub/sub: all socket servers listen to the same channel and pick out which messages they can send | |||
=== Box Office (BO) === | === Box Office (BO) === | ||
| Line 59: | Line 68: | ||
* Track connection state and share with Box Office | * Track connection state and share with Box Office | ||
* <b>Not behind Zeus</b> | * <b>Not behind Zeus</b> | ||