Lines Matching refs:message
84 <li>Able to generate message IDs to uniquely identify each message it sends. Message IDs
128 another message until the response is received.</li>
150 <li>HTTP: Supported in JSON message format.</li>
159 <p>This section gives an overview of sending messages. For details of message syntax,
165 server sends a message (the details vary depending on the platform):</p>
167 <li>The 3rd-party app server sends a message to GCM servers.</li>
168 <li>The GCM connection server enqueues and stores the message if the device is offline.</li>
169 <li>When the device is online, GCM connection server sends the message to the device.</li>
170 <li>The client app processes the message. </li>
180 <p>Required. When your app server sends a message in GCM, it must specify a target.</p>
184 When you send a message to multiple registration IDs, that is called a multicast message.</li>
197 message to a client app. See the <a href="{@docRoot}google/gcm/server-ref.html#table1">
201 <li>{@code collapse_key}: whether a message should be "send-to-sync" or a "message with
203 <li>{@code time_to_live}: setting an expiration date for a message.</li>
206 the message to the devices, you can set an optional HTTP parameter called
208 identical to running the request without this parameter, except that the message
210 IDs for the message and multicast parameters.</p>
215 <p>Optional. If you are including a payload in the message, you use the <code>data</code>
227 <p>Every message sent in GCM has the following characteristics:</p>
235 they are collapsed (where each new message replaces the preceding message) or not
236 collapsed (where each individual message is delivered). Every message sent in GCM
237 is either a "send-to-sync" (collapsible) message or a "message with
238 payload" (non-collapsible message).</p>
242 <p>A send-to-sync (collapsible) message is often a "tickle" that tells
245 pings the mobile application with a "New mail" message. This tells the
247 this message multiple times as new mail continues to accumulate, before the application
249 need to preserve every "New mail" message. One is sufficient. Another
251 Only the most recent message is relevant. </p>
262 <p>Unlike a send-to-sync message, every "message with payload"
263 (non-collapsible message) is delivered. The payload the message contains can be
264 up to 4kb. For example, here is a JSON-formatted message in an IM application in
276 <p>A "message with payload" is not simply a "ping" to the
278 application, for example, you would want to deliver every message, because every
279 message has different content. To specify a non-collapsible message, you simply
280 omit the <code>collapse_key</code> parameter. Thus GCM will send each message
284 are discarded from GCM, and a new message is created that tells the client how
299 to specify the maximum lifespan of a message.
302 deliver the message. Requests that don't contain this field default to the maximum
320 <p>When this happens, GCM will store the message and deliver it as soon as it's
322 a late message might as well never be delivered. For example, if the message is
324 small period of time before the call is terminated. Or if the message is an
327 <p>Another advantage of specifying the expiration date for a message is that GCM
354 contributors, and you want each of them to be able to send a message when they
355 publish a new article. This message might contain a URL so that the application
370 <p>When a 3rd-party server posts a message to GCM and receives a message ID back,
371 it does not mean that the message was already delivered to the device. Rather, it
372 means that it was accepted for delivery. What happens to the message after it is
377 the message will be delivered right away.</p>
379 <p>If the device is connected but idle, the message will still be
383 a message with the same collapse key (and registration ID) stored and waiting for
384 delivery, the old message will be discarded and the new message will take its place
385 (that is, the old message will be collapsed by the new one). However, if the collapse
392 a special message indicating that the limit was reached. The application can then
404 <p>If the device is not connected to GCM, the message will be stored until a
408 (for instance, if it was factory reset), the message will eventually time out and
412 <p>Finally, when GCM attempts to deliver a message to the device and the
413 application was uninstalled, GCM will discard that message right away and
414 invalidate the registration ID. Future attempts to send a message to that device
417 <p>Although is not possible to track the status of each individual message, the
428 periodically therefter. Each token is valid for a single message sent to
433 of message delivery for an application collapse key that sends a large