Confirmed users
1,340
edits
WebAPI/Push/Requirements: Difference between revisions
no edit summary
No edit summary |
|||
| (3 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
== Push Project Requirements == | == Push Project Requirements == | ||
<strike> | |||
* No open TCP sockets | * No open TCP sockets | ||
** 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. | ** 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 (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. | |||
** 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. | |||
* Multiple connections (signal versus signal+data) | * Multiple connections (signal versus signal+data) | ||
| Line 35: | Line 38: | ||
Non Goals: | Non Goals: | ||
* | * | ||
[[Category:Web APIs]] | |||