Protocols/MSNP/Tabs - Revision history

Animadoria at 09:24, 28 October 2022

2022-10-28T09:24:22Z

← Older revision		Revision as of 09:24, 28 October 2022
Line 9:		Line 9:
	In WLM 2009 MsgrConfig:		In WLM 2009 MsgrConfig:

	<~~pre~~>		<syntaxhighlight lang="xml"><?xml version="1.0" encoding="UTF-8" ?>
	<LocalizedConfig Market="fr-FR">		<LocalizedConfig Market="fr-FR">
	...		...
Line 34:		Line 34:
	...		...
	</LocalizedConfig>		</LocalizedConfig>
	</~~pre~~>		</syntaxhighlight>

	<code>LocalizedConfig</code> now carries its own <code>TabConfig</code> node, which carries a <code>slots</code> node defining all URLs WLM must load to retrieve each individual tab configuration.		<code>LocalizedConfig</code> now carries its own <code>TabConfig</code> node, which carries a <code>slots</code> node defining all URLs WLM must load to retrieve each individual tab configuration.

Animadoria at 13:24, 11 May 2022

2022-05-11T13:24:12Z

@@ Line 1: / Line 1: @@
-Convert from markdown:
+{{Protocols/MSNP}}
-<pre>
+Tabs are embedded websites on the Messenger client, set by the server.
 By WLM 2009, tabs are retrieved in a completely different manner compared to how it was performed on versions 8.5 and below.
 In WLM 2009 MsgrConfig:
-```xml
+<pre>
 <LocalizedConfig Market="fr-FR">
     ...
@@ Line 31: / Line 34: @@
     ...
 </LocalizedConfig>
-```
+</pre>
-`LocalizedConfig` now carries its own `TabConfig` node, which carries a `slots` node defining all URLs WLM must load to retrieve each individual tab configuration.
+<code>LocalizedConfig</code> now carries its own <code>TabConfig</code> node, which carries a <code>slots</code> node defining all URLs WLM must load to retrieve each individual tab configuration.
 Each URL defined is expected to return the following response, which has a similar format to the old MsgrConfig tab nodes:
-```xml
+<syntaxhighlight lang="xml"><?xml version="1.0" encoding="UTF-8" ?>
 <ads>
      <tabad>
@@ Line 50: / Line 52: @@
          <notificationid>0</notificationid>
      </tabad>
-</ads>
+</ads></syntaxhighlight>
-```
+Important nodes to note are <code>image</code>, <code>name</code>, <code>tooltip</code>, <code>contenturl</code>, and <code>hiturl</code>:
-Important nodes to note are `image`, `name`, `tooltip`, `contenturl`, and `hiturl`:
+== 8.5 and prior ==
-* `image` - Icon the tab will display on Messenger
-* `name`- Name of the tab's content (presumably for when the content is opened)
+In 8.5 and prior's MsgrConfig, it gets TabConfig from the MsgrConfig itself.
-* `tooltip` - Text the tab will display in its tooltip
-* `contenturl` - URL to load content from for the tab
+<pre>
-* `hiturl` - Assumed to aid in tracking how many people access the tab
+<TabConfig>
 </pre>

AD: Created page with "Convert from markdown:

 By WLM 2009, tabs are retrieved in a completely different manner compared to how it was performed on versions 8.5 and below.  In WLM 2009 MsgrCon..."

2021-03-13T06:15:54Z

Created page with "Convert from markdown: <pre> By WLM 2009, tabs are retrieved in a completely different manner compared to how it was performed on versions 8.5 and below. In WLM 2009 MsgrCon..."

New page

Convert from markdown:

<pre>
By WLM 2009, tabs are retrieved in a completely different manner compared to how it was performed on versions 8.5 and below.

In WLM 2009 MsgrConfig:

```xml
<LocalizedConfig Market="fr-FR">
...
<TabConfig>
<slots>
<URL id="1">
http://rad.msn.com/ADSAdClient31.dll?GetAd=&PG=IMFFTA
</URL>
<URL id="2">
http://rad.msn.com/ADSAdClient31.dll?GetAd=&PG=IMFFTB
</URL>
<URL id="3">
http://rad.msn.com/ADSAdClient31.dll?GetAd=&PG=IMFFTC
</URL>
<URL id="4">
http://rad.msn.com/ADSAdClient31.dll?GetAd=&PG=IMFFTD
</URL>
<URL id="5">
http://rad.msn.com/ADSAdClient31.dll?GetAd=&PG=IMFFTE
</URL>
...
</slots>
</TabConfig>
...
</LocalizedConfig>
```

`LocalizedConfig` now carries its own `TabConfig` node, which carries a `slots` node defining all URLs WLM must load to retrieve each individual tab configuration.

Each URL defined is expected to return the following response, which has a similar format to the old MsgrConfig tab nodes:

```xml
<?xml version="1.0" encoding="UTF-8" ?>
<ads>
<tabad>
<image>http://example.com/path/to/image.png</image>
<name>name</name>
<type>type</type>
<tooltip>tooltip</tooltip>
<contenturl>http://example.com/path/to/content</contenturl>
<hiturl>http://example.com/hiturl</hiturl>
<siteid>0</siteid>
<notificationid>0</notificationid>
</tabad>
</ads>
```

Important nodes to note are `image`, `name`, `tooltip`, `contenturl`, and `hiturl`:
* `image` - Icon the tab will display on Messenger
* `name`- Name of the tab's content (presumably for when the content is opened)
* `tooltip` - Text the tab will display in its tooltip
* `contenturl` - URL to load content from for the tab
* `hiturl` - Assumed to aid in tracking how many people access the tab
</pre>