From 76ab6c629079901d13041c34d2f17ea1dedea4d3 Mon Sep 17 00:00:00 2001 From: kmccormick Date: Tue, 23 Sep 2014 17:08:33 -0700 Subject: [PATCH] Doc update: Update preprod (staging) instructions. Fix for: b/17525318 Change-Id: Id93bd3e6e1fd5f203733121e3148cec8b24ab374 --- docs/html/google/gcm/ccs.jd | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-) diff --git a/docs/html/google/gcm/ccs.jd b/docs/html/google/gcm/ccs.jd index 1c7c8021b766d..2faf97f3829dd 100644 --- a/docs/html/google/gcm/ccs.jd +++ b/docs/html/google/gcm/ccs.jd @@ -81,10 +81,14 @@ Java sample using the Smack library.

The CCS XMPP endpoint runs at {@code gcm.googleapis.com:5235}. When testing functionality (with non-production users), you should instead connect to -{@code gcm-staging.googleapis.com:5236} (note the different port). Testing on -staging (a smaller environment where the latest CCS builds run) is beneficial -both for isolating real users from test code, as well as for early detection of -unexpected behavior changes.

+{@code gcm-preprod.googleapis.com:5236} (note the different port). Regular +testing on preprod (a smaller environment where the latest CCS builds run) is +beneficial both for isolating real users from test code, as well as for early +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.

The connection has two important requirements: