Confirmed users
1,018
edits
WebAPI/Push/Requirements: Difference between revisions
→Push Project Requirements
| Line 4: | Line 4: | ||
** In order to reduce network load, clients should not be required to hold a TCP socket open in order to receive notifications. | ** In order to reduce network load, clients should not be required to hold a TCP socket open in order to receive notifications. | ||
** Network operators should be able to use UDP broadcast (or other standarized mechanism, like WapPUSH, SMS) to 'wake up' client who then should establish a TCP connection to Push Server.</strike> | ** Network operators should be able to use UDP broadcast (or other standarized mechanism, like WapPUSH, SMS) to 'wake up' client who then should establish a TCP connection to Push Server.</strike> | ||
* No continuously open TCP sockets on mobile devices | * No continuously open TCP sockets on mobile devices (previous requirement obsoleted by WebRTC new server initiated connection requirement) | ||
** Connection between provider proxy to the Push server and the device will be determined by the provider. | ** Connection between provider proxy to the Push server and the device will be determined by the provider. | ||
** Provider must allow proxy to hold open a proxied socket to the Push Server, and must relay served notification alerts to devices in a timely manner. | ** Provider must allow proxy to hold open a proxied socket to the Push Server, and must relay served notification alerts to devices in a timely manner. | ||