Confirmed users
1,021
edits
WebAPI/SimplePush: Difference between revisions
Jump to navigation
Jump to search
→On the AppServer
No edit summary |
|||
| Line 134: | Line 134: | ||
How you associate endpoints to a given user is out of scope for this. You could have your own UserID that you use to map endpoints. Your client app could send both the old and new endpoints for an update, and you swap them in your data store. | How you associate endpoints to a given user is out of scope for this. You could have your own UserID that you use to map endpoints. Your client app could send both the old and new endpoints for an update, and you swap them in your data store. | ||
==== Return Codes ==== | |||
Return codes from the server match standard HTTP response codes: | |||
<table> | |||
<tr><th>Return Code</th><th>Explanation</th></tr> | |||
<tr><td>200</td><td>Notification has been accepted and passed on to client (via either direct connection or Proprietary Ping mechanism). This does not guarantee that the notification has been successfully delivered to the app, but does reflect a higher percentage chance of it happening.)</td></tr> | |||
<tr><td>202</td><td>Notification has been Accepted for delivery, but client is currently unavailable. The notification will be retained for when the client is available again, or the notification expires.</td></tr> | |||
<tr><td>400</td><td>The version value is incorrect or improperly formatted (e.g. "version=banana")</td></tr> | |||
<tr><td>403</td><td>Please be sure to use the PUT method when sending the Notification</td></tr> | |||
<tr><td>404</td><td>The endpoint is not valid and should not be retried.</td></tr> | |||
<tr><td>413</td><td>The data portion of the request is too large. (See reply text for maximum length.)</td></tr> | |||
</table> | |||
== DOM Interface == | == DOM Interface == | ||