Export (0) Print
Expand All

Cross-page Navigation

Starting with the release of the Windows Live Messenger Library version 3.0, the Windows Live Messenger Library and Messenger UI Controls support cross-page navigation. The Windows Live Messenger Web Toolkit maintains a user's Windows Live Messenger session across pages of the same site. The session information includes contact information and a user's instant messaging conversations.

Cross-page navigation is supported by the Windows Live Messenger Web Toolkit in the following browsers.

  • Microsoft Internet Explorer 6, Windows Internet Explorer 7, and Internet Explorer 8
  • Mozilla Firefox 1.5, 2.0, 3.0, and 3.5
    In Mozilla Firefox 1.5 and Safari 3.0, cross-page navigation is available only when Adobe Flash is installed.
  • Safari versions 3.0 and 4.0
  • Google Chrome versions 1.0, 2.0, and 3.0
    In Google Chrome, cross-page navigation is available only when Flash or Gears is installed.

Cross-page navigation uses the local storage available in the browser or in a browser plug-in. If a user has numerous contacts or long conversations, the Windows Live Messenger Web Toolkit may remove older information. For example, the Messenger Web Toolkit may remove the oldest instant messages as a user moves between pages.

The UI Controls support cross-page navigation. Applications can take advantage of the cross-page support without any special steps.

Windows Live Messenger Library applications should follow the guidelines in this section to handle cross-page navigation. Generally, each Windows Live Messenger Library application can implement the same logic on all pages of the application.

  1. An application should authenticate and sign in a user in the same way on every page. It does so by initializing an Identity object and calling User.SignIn with the Identity object.
    Notes   
    • The application can behave the same way on every page visit.
    • After the initial SignIn call on the first page that the user visits, subsequent SignIn calls on subsequent pages take place more quickly because the user is already signed in.
  2. An application initializes its contact list UI by listening for contact property updates after the sign-in process is completed. The application logic is the same whether it is the first page or a subsequent page.
  3. An application should reference the conversation collection to check for any existing conversations and to initialize conversation UI accordingly. The application should check the message history of each existing conversation and initialize the message history in each conversation UI object.
    Note   The Windows Live Messenger Library API adds a Reloaded property to the Conversation and Message objects. The Reloaded property is true if the conversation or message existed on a previous page.
Show:
© 2014 Microsoft