Android/frameworks_base
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

am a1572ffc: Merge "Doc update: Update preprod (staging) instructions." into klp-modular-docs

Browse Source 
* commit 'a1572ffc6b8df1f0da637fdb93b949322fcb3637':
  Doc update: Update preprod (staging) instructions.
This commit is contained in:
kmccormick
2014-10-01 17:08:13 +00:00
committed by Android Git Automerger
parent 781c988a76 a1572ffc6b
commit ae3bd63bc5
1 changed files with 8 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
docs/html/google/gcm/ccs.jd
View File

@@ -81,10 +81,14 @@ Java sample using the Smack library</a>.</p>
<p>The CCS XMPP endpoint runs at {@code gcm.googleapis.com:5235}. When testing <p>The CCS XMPP endpoint runs at {@code gcm.googleapis.com:5235}. When testing
functionality (with non-production users), you should instead connect to functionality (with non-production users), you should instead connect to
{@code gcm-staging.googleapis.com:5236} (note the different port). Testing on {@code gcm-preprod.googleapis.com:5236} (note the different port). Regular
staging (a smaller environment where the latest CCS builds run) is beneficial testing on preprod (a smaller environment where the latest CCS builds run) is
both for isolating real users from test code, as well as for early detection of beneficial both for isolating real users from test code, as well as for early
unexpected behavior changes.</p> detection of unexpected behavior changes. Note that a connection receives upstream
messages destined for its GCM sender ID, regardless of which environment (gcm or
gcm-preprod) it is connected to. Therefore, test code connecting to
{@code gcm-preprod.googleapis.com:5236} should use a different GCM sender ID to
avoid upstream messages from production traffic being sent over test connections.</p>
<p>The connection has two important requirements:</p> <p>The connection has two important requirements:</p>