WebAPI/Push/Requirements: Difference between revisions

From MozillaWiki
< WebAPI‎ | Push
Jump to navigation Jump to search
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 verses signal+data)
* 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

Revision as of 13:08, 9 November 2012

Push Project Requirements

  • 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.
    • 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 versus signal+data)
    • Push system should not require a second TCP connection for data/notification fetching
      • Mozilla believe that this may be a premature optimization.
  • Easy-to-use API
    • A design goal for *all* web apis.
    • Default should be safe, and ensures end to end privacy of data
    • Must not require applications to do their own crypto
  • Guaranteed delivery
    • Push system should guaranteed a timely delivery of notification
    • Push system should be able to recover from data center loss
  • Data privacy
    • Push server should not be able to inspect application private data
  • Push system scalability
    • Push system must be able to be scaled to tens of millions.
      • Order of mag smaller than apple or android's system.
    • System must be allowed to support multiple (and possibly federated) push servers