Home
last modified time | relevance | path

Searched refs:canonical (Results 1 – 7 of 7) sorted by relevance

/frameworks/base/docs/html/google/gcm/
Dhttp.jd197 <td>Number of results that contain a canonical registration ID. See
198 <a href="adv.html#canonical">Advanced Topics</a> for more discussion of this topic.</td>
210 message but it has another canonical registration ID for that device, so sender
230 the new value (canonical ID) in your server database. Note that the original ID
256 has the format of <code>registration_id=<em>canonical ID</em></code>. The second
426 without canonical IDs in the response:</p>
441 with 3 messages successfully processed, 1 canonical registration ID returned,
Dadv.jd21 <li><a href="#canonical">Canonical IDs</a></li>
149 <h3 id="canonical">Canonical IDs</h3>
154 <p>GCM provides a facility called &quot;canonical registration IDs&quot; to easily
155 recover from these situations. A canonical registration ID is defined to be the ID
159 will process the request as usual, but it will include the canonical registration
161 the registration ID stored in your server with this canonical ID, as eventually
Dhelper.jd184 … but the result returned a canonical registration ID, it's necessary to replace the current regist…
Dc2dm.jd76 … ID to your server anymore. For more information, see <a href="adv.html#canonical">Advanced Topics…
/frameworks/base/media/java/android/mtp/
DMtpDatabase.java308 String canonical = f.getCanonicalPath(); in inStorageRoot() local
310 if (canonical.startsWith(root)) { in inStorageRoot()
/frameworks/base/docs/html/training/id-auth/
Dcustom_auth.jd64 all.) The third requirement has a canonical, and rather simple,
/frameworks/base/docs/html/guide/topics/connectivity/nfc/
Dnfc.jd685 android.nfc.NdefRecord#TNF_EXTERNAL_TYPE} have a canonical format of: