CloudServices/FirefoxMobileServices/ChannelService: Difference between revisions

CloudServices/FirefoxMobileServices/ChannelService (view source)

Revision as of 22:17, 15 May 2014

289 bytes added , 15 May 2014

no edit summary

Bbangert

Confirmed users

192

edits

@@ Line 17: / Line 17: @@
 To develop a single multiplexed communication channel between clients and Mozilla Cloud Services.
-This should result in:
+This will result in:
 * Client-side API for client-side code that needs to talk to a Mozilla Cloud Service
@@ Line 25: / Line 25: @@
 * Easier updates of client-side code that is not intermixed with channel code
 * Ability to update channel code for efficiency/performance/cost-savings without changing other client-side or Cloud Services server-side code
+* Isolates the scalability challenge of holding open vast amounts of connections to ChannelService, simplifying development of additional services
 ==Use Cases==
@@ Line 30: / Line 31: @@
 === Push ===
-The first candidate for using the ChannelService is [https://wiki.mozilla.org/WebAPI/SimplePush Push], which is already on FxOS. At the moment the code handling the
+The first candidate for using the ChannelService is [https://wiki.mozilla.org/WebAPI/SimplePush Push], which is already on FxOS. At the moment the code handling the socket connection is mixed in with the code handling the DOM API's for Push. By splitting the channel out, future Push updates could be easier to land in the client. The server architecture will also be drastically simplified by no longer needing to handle the scaling challenge of all the socket connections.
-socket connection is mixed in with the code handling the DOM API's for Push. By splitting the channel out, future Push
-updates could be easier to land in the client.
 === Presence ===