Confirmed users
1,022
edits
CloudServices/Roadmaps/SimplePush-Server: Difference between revisions
Jump to navigation
Jump to search
CloudServices/Roadmaps/SimplePush-Server (view source)
Revision as of 15:42, 30 September 2013
, 30 September 2013→Goals
(→Goals) |
|||
| Line 9: | Line 9: | ||
==Goals== | ==Goals== | ||
It's quite easy for remote devices to connect back to a server, but it's difficult for the server to connect back to the remote devices. This is even more true with mobile devices. Maintaining a lot of individual port connections (even if they're just polling) can lead to very short battery lives. | |||
Simplepush attempts to address this by having a single port connection maintained back to a central server. Applications register a callback with SimplePush, which returns a URL that can be passed to the remote server. As interesting things happen, the remote server can check to see if there's a live connection to the App, and if not, can use the URL to wake the remote app. | |||
SimplePush is based off of [http://research.google.com/pubs/pub37474.html Thialfi]. This system manages version numbers for assigned channels. In short: A client checks to see if it's version matches what's on the push server. If so, do nothing, if not, go fetch from the app server. | SimplePush is based off of [http://research.google.com/pubs/pub37474.html Thialfi]. This system manages version numbers for assigned channels. In short: A client checks to see if it's version matches what's on the push server. If so, do nothing, if not, go fetch from the app server. | ||