Message Format
This content is no longer actively maintained. It is provided as is, for anyone who may still be using these technologies, with no warranties or claims of accuracy with regard to the most recent product version or service release.
In the Live Meeting service API, most messages are formatted as XML elements. The different elements require the following formats.
For more information about message formats, see the PlaceWareConfCenter element in the Live Meeting service API Reference.
Request Element
<PlaceWareConfCenter
authUser="string"
authPassword="string">
<*Request>...</*Request>
</PlaceWareConfCenter>
- or -
<PlaceWareConfCenter
authTicket="string">
<*Request>...</*Request>
</PlaceWareConfCenter>
The asterisk (*) is the placeholder of the name of a message.
Reply Element
<PlaceWareConfCenter>
<*Reply>...</*Reply>
</PlaceWareConfCenter>
Here the asterisk (*) is the placeholder of the name of a message.
Note
No attributes are present in the PlaceWareConfCenter element.
Error Element
<PlaceWareConfCenter>
<Fault>...</Fault>
</PlaceWareConfCenter>
Note
No attributes are present in the PlaceWareConfCenter Element element.
Informational and Warning Element
The following code shows the format of an informational and warning message.
<PlaceWareConfCenter>
<InfoWarn>...</InfoWarn>
</PlaceWareConfCenter>
Note
No attributes are present in the PlaceWareConfCenter Element element.
Special Messages
In the Live Meeting service API, there are three special messages that are not represented as XML elements:
The initial session request to retrieve the URL of a specified Live Meeting conference center. For more information, see the GetPostingURL message.
A request for the mass transfer of bulk data. For more information, see Mass Transfer. These messages are sent using an HTTPS GET or HTTPS POST call.
A request for the customized link values set in Live Meeting Manager. For more information, see GetCustomizedLinksMessage.