Difference between revisions of "SOAP transport"
From A-SMIL.org
(→Related: Reference to Hornet 1.0) |
|||
(One intermediate revision by the same user not shown) | |||
Line 1: | Line 1: | ||
+ | Applicable device : IAdea XMP-3000 series | ||
+ | |||
SMIL media players often also provide a network interface based on [[wikipedia:SOAP|SOAP]] (historically short for "Simple Object Access Protocol"). | SMIL media players often also provide a network interface based on [[wikipedia:SOAP|SOAP]] (historically short for "Simple Object Access Protocol"). | ||
Line 19: | Line 21: | ||
* '''Play()''': play a SMIL | * '''Play()''': play a SMIL | ||
+ | |||
+ | == Transport Authentication == | ||
+ | |||
+ | The AdAPI uses HTTP Digest authentication to protect its transactions. The default user name is "admin" and password "" (empty string). | ||
== Related == | == Related == |
Latest revision as of 09:26, 29 June 2017
Applicable device : IAdea XMP-3000 series
SMIL media players often also provide a network interface based on SOAP (historically short for "Simple Object Access Protocol").
Contents
SOAP Interfaces
A typical SOAP network API supports the following objects and methods from a digital signage media player:
Session
- Login(): initiate a new command session
- Logout(): end a command session
ContentManager
- CreateObject(): upload a file into the media player
- FindObjet(): enumerate files in the media player
- RemoveResource(): delete a file in the media player
MediaControl
- Play(): play a SMIL
Transport Authentication
The AdAPI uses HTTP Digest authentication to protect its transactions. The default user name is "admin" and password "" (empty string).
Related
Programming tools including the Visual Studio Express directly suports making SOAP calls from Windows. More information is available below.
- Managing SMIL players from Visual Studio Express
- Sample project: Hornet 1.0
- WSDL description of the SOAP interface