diff options
| author | 2012-08-01 16:14:47 -0700 | |
|---|---|---|
| committer | 2012-08-01 16:14:47 -0700 | |
| commit | a65d0e78ddf6e70a348b8a6dea39337e6e17a494 (patch) | |
| tree | 5d70e37176de2fa6e207a210d2280e1a47c01e2a | |
| parent | 2b1584c1d53cd1070d5157c07158828b4baf8844 (diff) | |
Doc change: 4K -> 4kb
Change-Id: Ic563436062c6bd17ba87f3b3cc4c765972b07289
| -rw-r--r-- | docs/html/guide/google/gcm/adv.jd | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/html/guide/google/gcm/adv.jd b/docs/html/guide/google/gcm/adv.jd index 39e946ee34e0..5cb433f4f58d 100644 --- a/docs/html/guide/google/gcm/adv.jd +++ b/docs/html/guide/google/gcm/adv.jd @@ -203,7 +203,7 @@ registerReceiver(mRetryReceiver, filter); <p>GCM allows a maximum of 4 different collapse keys to be used by the GCM server at any given time. In other words, the GCM server can simultaneously store 4 different send-to-sync messages, each with a different collapse key. If you exceed this number GCM will only keep 4 collapse keys, with no guarantees about which ones they will be.</p> <h3 id="payload">Messages with payload</h3> -<p>Unlike a send-to-sync message, every "message with payload" (non-collapsible message) is delivered. The payload the message contains can be up to 4K. For example, here is a JSON-formatted message in an IM application in which spectators are discussing a sporting event:</p> +<p>Unlike a send-to-sync message, every "message with payload" (non-collapsible message) is delivered. The payload the message contains can be up to 4kb. For example, here is a JSON-formatted message in an IM application in which spectators are discussing a sporting event:</p> <pre class="prettyprint pretty-json">{ "registration_id" : "APA91bHun4MxP5egoKMwt2KZFBaFUH-1RYqx...", |