172
edits
WebAPI/Push/Requirements: Difference between revisions
m
→Push Project Requirements
Willyaranda (talk | contribs) No edit summary |
|||
| Line 5: | Line 5: | ||
** 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. | ||
* Multiple connections (signal | * Multiple connections (signal versus signal+data) | ||
** Push system should not require a second TCP connection for data/notification fetching | ** Push system should not require a second TCP connection for data/notification fetching | ||
*** Mozilla believe that this may be a premature optimization. | *** Mozilla believe that this may be a premature optimization. | ||
| Line 24: | Line 24: | ||
** Push system must be able to be scaled to tens of millions. | ** Push system must be able to be scaled to tens of millions. | ||
*** Order of mag smaller than apple or android's system. | *** Order of mag smaller than apple or android's system. | ||
** System must be allowed to support multiple push servers | ** System must be allowed to support multiple (and possibly federated) push servers | ||