From 507c3129eb3f222d21f8b46f85fe1c7d2a7d0ac6 Mon Sep 17 00:00:00 2001 From: Katie McCormick Date: Tue, 10 Jul 2012 15:12:38 -0700 Subject: [PATCH] Doc change: New TTL error code. Change-Id: I99844d28243e0d6592219f532db08855d73f338e --- docs/html/guide/google/gcm/gcm.jd | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/docs/html/guide/google/gcm/gcm.jd b/docs/html/guide/google/gcm/gcm.jd index d871fb4a94029..388424449aab3 100644 --- a/docs/html/guide/google/gcm/gcm.jd +++ b/docs/html/guide/google/gcm/gcm.jd @@ -620,7 +620,7 @@ messages. Authorization:key=AIzaSyB-1uEai2WiUapxCs2Q0GZYzPu7Udno5aA { - "registration_id" : "APA91bHun4MxP5egoKMwt2KZFBaFUH-1RYqx...", + "registration_ids" : ["APA91bHun4MxP5egoKMwt2KZFBaFUH-1RYqx..."], "data" : { ... }, @@ -874,7 +874,10 @@ messages.
  • Implement exponential back-off in your retry mechanism. This means an exponentially increasing delay after each failed retry (e.g. if you waited one second before the first retry, wait at least two second before the next one, then 4 seconds and so on). If you're sending multiple messages, delay each one independently by an additional random amount to avoid issuing a new request for all messages at the same time.
  • Senders that cause problems risk being blacklisted. -
    Happens when the HTTP status code is 500 or 503; or when the error field of a JSON object in the results array is Unavailable. +
    Happens when the HTTP status code is 500 or 503, or when the error field of a JSON object in the results array is InternalServerError or Unavailable. + +
    Invalid Time To Live
    +
    The value for the Time to Live field must be an integer representing a duration in seconds between 0 and 2,419,200 (4 weeks). Happens when error code is InvalidTtl.

    Example responses