Messages
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.
The Microsoft Office Live Meeting service API is a message-based protocol that uses HTTPS for message transport. A Live Meeting message consists of the following:
A request sent by a client application to a given conference center.
A reply returned to the client from the conference center. The reply can contain a successful query result or an error message when the request cannot be processed.
Except for the GetPostingURL, Mass Transfer, and GetCustomizedLinksMessage messages, all Live Meeting messages are XML elements based on a specific XML vocabulary.
Whenever you want to perform an operation, you issue an appropriate command to a Live Meeting conference center. This command is packaged in a message. When your request is received, the Live Meeting service parses the incoming message and attempts to carry out the requested operation in the targeted conference center. The service replies with a message indicating the success or failure of the request. In Live Meeting, messages are packaged as XML elements.
Example: Typical Message
The CreateMeeting message is a typical one in the Live Meeting service API. It consists of a request component and a reply component. The request component is represented by a CreateMeetingRequest XML element and the reply component is represented by a CreateMeetingReply element when the request is successfully processed. If an error occurs in processing the request, a Fault element containing error information is returned.
Example: GetPostingURL Is a Special Message
In the GetPostingURL message, the request part is an HTTPS GET with GetPostingURLRequest as part of a special URL. The reply part of this message, however, is an XML element (GetPostingURLReply) when the request is processed successfully.
Example: Mass Transfer Is Another Special Message
For the mass transfer of bulk data (for example, uploading a presentation or downloading a meeting recording), a resource-specific URL is first fetched using GetURLRequest. The resulting URL is then used to GET or POST the specified resource. After the resource is posted, the conference center returns a MassTransferReply element. This element contains an InfoWarnFaultList child element indicating the success or failure of the post operation for the mass transfer.
For more information about these elements and messages, see Live Meeting service API Reference.
In This Section
Subject |
Description |
|---|---|
Describes the use of input parameters in a request and the expected response from a conference center when the request is processed successfully. |
|
Describes the basic process for fault or diagnostic messages that are returned instead of a message reply when a conference center cannot fulfill a request. |
|
Describes notational conventions to specify attribute values and element contents. |
|
Outlines different requirements and behaviors for trimming, user IDs, group IDs, meeting and recording names, user passwords, meeting passwords, Live Meeting UI considerations, and general UI considerations. |
|
Describes different formats for different messages. |
|
Provides examples to show how message operations work. |