Overview

When invoking an application, the Social Container sends across a context. The context contains information that the application needs to operate against one or more social networks.

Design

The following attributes will be part of the application context:

All the Facebook signature fields:

• in_canvas
• request_method
• locale
• position_fix
• time
• added
• user
• profile_update_time
• session_key
• expires
• friends
• api_key
• is_ajax (when invoked via Ajax proxy)

Plus the following Ringside signature fields: 

• flavor - the flavor of the rendering. Currently, applications could be sent "canvas" (the default), "sidebar", or "menu".
• network - the originating (Host) network for the request. For a single-Ringside deployment, this will always be the social API key for your Ringside server.
• principal - the mapped principal ID for the logged-in user. This may be empty or missing if the application does not require identity mapping.
• network_rest_url - the URL used to submit API requests to the originating (Host) network
• network_login_url - the URL used to redirect to the originating (Host) network to perform user authentication. This page must conform to the Facebook login protocol (all Ringside servers do)
• network_canvas_url - the URL used to redirect to the originating (Host) network to perform redirects to the application's canvas page (after appending its own canvas_url fragment)