Table of Contents

When the User Loads an App...

The illustration below outlines the process followed each time an App is loaded.

when_user_loads_an_app.jpg

  1. When an App is loaded, a call is made to the 3rd party developer’s server. For example, when the Share Your Mood App is loaded, the Rediff Apps server makes a call to www.x.com/share-your-mood, which is the callback URL for this App.
  2. Calls to 3rd party developer’s server from the Rediff Apps server:
    1. Whenever an App is loaded, the Rediff Apps server sends an Initialization XML(as shown below) in the POST field to the App's callback URL. The Initialization XML will have the following structure.
      <?xml version="1.0"?>
            <initialcall>
                    <userid>XXXXXXXXXX</userid>
            </initialcall>

Also X-REDF-UID, X-REDF-AUTHKEY, X-REDF-UAUTH variables is set in Header.

  1. All calls from the App should go to the 3rd party developer’s server i.e. Callback URL, or to other Rediff Services, such as MyPage or Pages.
  2. The 3rd party developer’s server will build the App using the data and patterns from the Rediff API server.
    note_icon_3.jpgAll calls to the Rediff API server should include the user’s ID, the Apps AuthKey and the AppKey.
  3. The App built in (Step 3) will be returned to the Rediff Apps server.
  4. The Rediff Apps server renders your App in the user’s window.

CLICK HERE to return to the main Table of Contents.

get_acquainted_with_the_lifecycle_of_the_app_-_user_s_perspective.txt · Last modified: 2010/11/02 15:55 by Sagar
Back to top
CC Attribution-Noncommercial-Share Alike 3.0 Unported
chimeric.de = chi`s home Valid CSS Driven by DokuWiki do yourself a favour and use a real browser - get firefox!! Recent changes RSS feed Valid XHTML 1.0