Lines Matching refs:as
65 Smack</a> demo apps as a starting point.</li>
92 <li>GCM HTTP: 3rd-party app servers send messages as HTTP POST requests and
104 <li>GCM HTTP: JSON messages sent as HTTP POST.</li>
118 <li>Able to handle requests and resend them as needed, using
147 <p>For HTTP you must specify the target as one of:</p>
155 <li>You must specify the target as the "to" field, where the "to"
214 A 3rd-party server can use {@code notification_key} as the target for a message
224 <td>An arbitrary string (such as "Updates Available") that is used
247 included in the Intent as application data, with the key being the extra's name.
254 (such as integers or booleans), you have to do the conversion to string yourself.
257 some reserved words (such as <code>collapse_key</code>) that are technically
260 words that are defined as field names in this table is not recommended, even in
275 device is offline. Optional (default time-to-live is 4 weeks, and must be set as
305 <p>If you are using plain text instead of JSON, the message fields must be set as
306 HTTP parameters sent in the body, and their syntax is slightly different, as
320 <td>Same as JSON (see previous table). Optional.</td>
325 <td>Payload data, expressed as parameters prefixed with <code>data.</code> and
326 suffixed as the key. For instance, a parameter of <code>data.score=3x1</code> would
332 (such as <code>collapse_key</code>) that are technically allowed in payload data.
334 overwrite the value in the payload data. Hence using words that are defined as
341 <td>Should be represented as <code>1</code> or <code>true</code> for
347 <td>Same as JSON (see previous table). Optional.</td>
351 <td>Same as JSON (see previous table). Optional.
356 <td>Same as JSON (see previous table). Optional.
370 in a <code>com.google.android.c2dm.intent.RECEIVE</code> Intent as a set of