Protocols/MSNP/Activities/SDK/Sandbox: Difference between revisions
Animadoria (talk | contribs) (Created automatically by Anima Importer) |
Animadoria (talk | contribs) No edit summary |
||
| Line 6: | Line 6: | ||
A MSN® Messenger Activity runs in a confined program space, in which the application is only allowed to use certain specific resources.<br /> | A MSN® Messenger Activity runs in a confined program space, in which the application is only allowed to use certain specific resources.<br /> | ||
<br /> | <br /> | ||
Some Activities need features in addition to the basic features or allowed resources; these additional features are called <span class="clsGlossaryTerm">advanced capabilities</span>. Similar to the way ActiveX® controls can be signed with additional rights, applications can be granted certain additional permissions. In the [[Protocols/MSNP/Activities/SDK/ | Some Activities need features in addition to the basic features or allowed resources; these additional features are called <span class="clsGlossaryTerm">advanced capabilities</span>. Similar to the way ActiveX® controls can be signed with additional rights, applications can be granted certain additional permissions. In the [[Protocols/MSNP/Activities/SDK/Techref/Objectmodel/Index|Activity API Object Model]] section of this documentation, features that require special permissions are labeled ''restricted''.<br /> | ||
<br /> | <br /> | ||
Advanced capabilities are available only to applications that have undergone careful testing and have been approved by Microsoft. Even then, each capability is permitted individually. It is possible to have an application that is only allowed to read the user name of the currently logged-on user. Another application may be able to parse any incoming instant messages from a remote party. Some advanced applications will require combinations of advanced capabilities, but the majority of applications will run inside the confined program space.<br /> | Advanced capabilities are available only to applications that have undergone careful testing and have been approved by Microsoft. Even then, each capability is permitted individually. It is possible to have an application that is only allowed to read the user name of the currently logged-on user. Another application may be able to parse any incoming instant messages from a remote party. Some advanced applications will require combinations of advanced capabilities, but the majority of applications will run inside the confined program space.<br /> | ||
<br /> | <br /> | ||
For further discussion on using advanced capabilities, see [[Protocols/MSNP/Activities/SDK/ | For further discussion on using advanced capabilities, see [[Protocols/MSNP/Activities/SDK/Techref/Flags/Index|Obtaining Access to Restricted Features]]. | ||
Latest revision as of 22:46, 12 August 2022
Standard vs. Advanced Applications
A MSN® Messenger Activity runs in a confined program space, in which the application is only allowed to use certain specific resources.
Some Activities need features in addition to the basic features or allowed resources; these additional features are called advanced capabilities. Similar to the way ActiveX® controls can be signed with additional rights, applications can be granted certain additional permissions. In the Activity API Object Model section of this documentation, features that require special permissions are labeled restricted.
Advanced capabilities are available only to applications that have undergone careful testing and have been approved by Microsoft. Even then, each capability is permitted individually. It is possible to have an application that is only allowed to read the user name of the currently logged-on user. Another application may be able to parse any incoming instant messages from a remote party. Some advanced applications will require combinations of advanced capabilities, but the majority of applications will run inside the confined program space.
For further discussion on using advanced capabilities, see Obtaining Access to Restricted Features.