Confirmed users
1,022
edits
CloudServices/SimplePushServer: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
|||
| Line 14: | Line 14: | ||
<i>How will this be used?</i> | <i>How will this be used?</i> | ||
==Requirements== | ==Requirements== | ||
* APP requests an ENDPOINT from the PUSH CLIENT and shall register two callback functions, one for receipt of the ENDPOINT, and a second for handling of a VERSION EVENT | * APP requests an ENDPOINT from the PUSH CLIENT and shall register two callback functions, one for receipt of the ENDPOINT, and a second for handling of a VERSION EVENT | ||
* If not already present, PUSH CLIENT shall generate a unique UUID4 Identifier for the UserAgent (UAID) | * If not already present, PUSH CLIENT shall generate a unique UUID4 Identifier for the UserAgent (UAID) | ||
| Line 52: | Line 41: | ||
NOTE: a PUSH RELAY may be created by combining the polling aspects of the PUSH CLIENT with the data management and KICK driver of the PUSH SERVER. This would allow a VERSION EVENT system to enter protected networks or use restricted means to communicate to USER AGENTs. It is important to note that once a PUSH SERVER has received an ACK for a given UAID, the PUSH SERVER is under no obligation to retain that data, and proper relay of the VERSION EVENT is the PUSH RELAY's problem. | NOTE: a PUSH RELAY may be created by combining the polling aspects of the PUSH CLIENT with the data management and KICK driver of the PUSH SERVER. This would allow a VERSION EVENT system to enter protected networks or use restricted means to communicate to USER AGENTs. It is important to note that once a PUSH SERVER has received an ACK for a given UAID, the PUSH SERVER is under no obligation to retain that data, and proper relay of the VERSION EVENT is the PUSH RELAY's problem. | ||
==Get Involved== | |||
<i>Call to action for folks who want to help.</i> | |||
=Design= | |||
==Points of Contact== | |||
Server Engineer - <i>"trink"</i> <i>trink@mozilla</i> | |||
Server Engineer - <i>JR Conlin</i> <i>jrconlin@mozilla</i> | |||
Client Engineer - | |||
==API Reference/Documentation== | |||
=== Data Schema === | === Data Schema === | ||
<i>How will data be stored</i> | <i>How will data be stored</i> | ||