Confirmed users
192
edits
CloudServices/FirefoxMobileServices/ChannelService: Difference between revisions
CloudServices/FirefoxMobileServices/ChannelService (view source)
Revision as of 18:44, 6 June 2014
, 6 June 2014→Cloud Services Channel Service
| Line 168: | Line 168: | ||
* Routing inbound-client messages to the appropriate Services Inbound Relay (Push/etc) | * Routing inbound-client messages to the appropriate Services Inbound Relay (Push/etc) | ||
* Routing outbound-client messages received from Outbound Routers | * Routing outbound-client messages received from Outbound Routers | ||
* | * Broadcasting to the Outbound Router indicating what DeviceID's are connected to this node | ||
* Holding very high quantities of connections to clients | * Holding very high quantities of connections to clients | ||
| Line 179: | Line 178: | ||
Inbound relays are responsible for: | Inbound relays are responsible for: | ||
* Accepting messages from connection nodes for | * Accepting messages from connection nodes for services | ||
* Spooling a small amount of messages if a service is not available to relay them to | * Spooling a small amount of messages if a service is not available to relay them to | ||
==== Outbound Router ==== | ==== Outbound Router ==== | ||
| Line 187: | Line 185: | ||
Outbound routers are responsible for: | Outbound routers are responsible for: | ||
* | * Using their local mapping to determine what ConnectionNode to deliver to for a DeviceID | ||
* Holding connections to ConnectionNode's for message delivery | * Holding connections to ConnectionNode's for message delivery | ||
* Sending messages to deliver to ConnectionNode's and indicating whether they were delivered or not | * Sending messages to deliver to ConnectionNode's and indicating whether they were delivered or not | ||
* Informing the service if a device id is | * Informing the service if a device id is not connected | ||
===Push Server Modifications=== | ===Push Server Modifications=== | ||