Application Context

The context passed into your application has a few parameters and we continue to work on the right set of context to pass into an application on each request. The main object is called RingsideSocialAppContext. These parameters are passed from the SOCIAL layer to your APPLICATION as POST parameters.

• Each parameter is prefixed with fb_sig_ though this can be overridden in the system.
• Other parameters can be added (add a JIRA if you see a need for more)

Facebook standard parameters

• api_key - Application key

• iframe - Is this application executed as an iframe application

• in_canvas - is this being rendered in the canvas page. In this case the flavor should be public function setInCanvas( $value )

• added - Is the application being invoked added to the current user

• user - the user id of the calling user

• session_key - the session key to be used in making calls to the API server

• profile_update_time - the last time the users profile was updated (not currently implemented)

• expires - time session expires

• request_method - the type of incoming request GET or POST. Requests sent to an APP are POST, but this request_method parameter represents the request into the Ringside Server.

• time - the current time of the invocation.

Ringside specific

• flavor - The application can be asked to be rendered in different flavors for example - MENU, CANVAS, SIDEBAR, WIDGET.
  We are considering removing this and move to a pure URL based configuration for these flavors. This would approximate the facebook model but add to configuration settings.

• network_id - related to identity mapping this defines the network which invoked the call. (ie a Ringside server or Facebook or ... ). This should be part of each call.

• nuser - principal id. The identification of the users which does not map to a specific social network, but allows internal mappings. If the user does not have a principal and this is single system without support for external sites then its not passed through.

• soc_session_key - Social Session Key represents the relationship between the network, ringside and the user. Similar to how session_Key works between an application and the APIs this is the relationship between a network and the Ringside Social server tied to a specific user. Each request should have a social session key.

Note: All parameters are prefixed with fb_sig_, for example flavor is fb_sig_flavor.

We are currently working on anonymous support, calling an application anonymously and supporting requests to the api server for such. This might impact the applications and some fields might not be present. More to come.