Difference between revisions of "Protocols/MSNP/Activities"

From NINA Wiki
Jump to navigation Jump to search
 
Line 27: Line 27:
  
 
The SDK itself is available here, archived on the Wayback Machine too: http://web.archive.org/web/20051104052000/http://download.microsoft.com/download/2/c/3/2c300000-e774-4e80-9682-9a01109fd309/messengerActivitySDK.zip
 
The SDK itself is available here, archived on the Wayback Machine too: http://web.archive.org/web/20051104052000/http://download.microsoft.com/download/2/c/3/2c300000-e774-4e80-9682-9a01109fd309/messengerActivitySDK.zip
 +
 +
'''See also''': [[Protocols/MSNP/Activities/SDK]]
  
  

Latest revision as of 22:31, 11 September 2022

MSNP Protocol
IntroductionTermsClients
Reference
Error ListCommandsRelying Party SuiteSpotlife
Services
XMPPHTTP GatewayTabsActivities
Documentation
Development ToolsMSNP Grid
PolygamyURLs used by MSN
Documents
Protocol Versions
Version 21
Version 18
Version 16
Version 15
Version 14
Version 13
Version 12
Version 11
Version 9
Version 8
Version 2
MSNC
IntroductionP2PObject DescriptorDisplay PicturesFile Transfer
Scenarios
Microsoft Messenger for Mac
MSNP on WebTV (MSNTV)

Here is some information on the inner workings of MSN Messenger Activities.

How it works

The MsgrConfig XML that is retrieved from the Escargot server contains 3 Activity-related URLs:

<AppDirConfig>
  <AppDirPageURL>
    http://appdirectory.messenger.msn.com/AppDirectory/Directory.aspx?L=en-us
  </AppDirPageURL>
  <AppDirSeviceURL>
    http://appdirectory.messenger.msn.com/AppDirectory/AppDirectory.asmx
  </AppDirSeviceURL>
  <AppDirVersionURL>
    http://appdirectory.messenger.msn.com/AppDirectory/GetAppdirVersion.aspx
  </AppDirVersionURL>
</AppDirConfig>

The App Directory Service is a SOAP service. It’s mainly used for loading Activity info and starting with MSN 7.0, loading featured Activities. Along with that, its WSDL (the XML interface definition XML that describes the SOAP service’s requests and responses) is available to read at this archived link from the Wayback Machine:

http://web.archive.org/web/20050311202052id_/http://appdirectory.messenger.msn.com:80/AppDirectory/AppDirectory.asmx?WSDL

There is also some information regarding the Entry node defined by the WSDL here: http://web.archive.org/web/20110424131207/http://msdn.microsoft.com/en-us/library/aa751073.aspx

Here’s part of the Activity documentation from the “Windows Live Messenger Activity SDK” MSDN page: http://web.archive.org/web/20110905024714/http://msdn.microsoft.com/en-us/library/aa751024.aspx

The SDK itself is available here, archived on the Wayback Machine too: http://web.archive.org/web/20051104052000/http://download.microsoft.com/download/2/c/3/2c300000-e774-4e80-9682-9a01109fd309/messengerActivitySDK.zip

See also: Protocols/MSNP/Activities/SDK


The App Directory

MSN 6

The App Directory page (The pane that was loaded when you clicked on the “Activities” button in 6.0 - 6.2) is archived on the Wayback Machine as well: http://web.archive.org/web/20051220110746id_/http://appdirectory.messenger.msn.com:80/AppDirectory/Directory.aspx?L=en-us

Speaking of which, it needs 5 images it uses for its layout:

Our understanding of how this page worked is when a user clicked on the “Activities” menu:

  1. Because the Activities menu is actually an HTML page, a JavaScript function would transmit the Activity ID to MSN Messenger (via window.external).
  2. MSN Messenger would query the App Directory SOAP Service using the GetAppEntry method with the requested Activity ID as a par