Communication protocols

The following table describes communication between the components involved in push functionality.
Source Destination Protocol Description and Timeouts
User agent (browser) Push server (application server)

HTTPS

One-way SSL with a server side certificate

The push server brokers the establishment of an initial push session. The push server authenticates the user and provides the location of a push redirector to the user agent, along with a unique client ID.
User agent (browser) Push redirector

HTTPS/Comet

One-way SSL with a server side certificate

The user agent uses the Comet model to establish a long-held HTTP connection with the redirector to enable the push redirector to push data to the browser.

Push redirector Push server (application server)

HTTPS

One-way SSL with a server side certificate

The push server communicates with the push redirector to push information to users. The push server also brokers a three-way handshake between the user agent and the push redirector when initializing a push session.