Compartilhar via


Getting Posting URL

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.

Using the Live Meeting service API follows this general programming pattern:

  1. You call an HTTPS GET with a URL of the "www.livemeeting.com/cc/ <conference_center> /xml/<version>/GetPostingURLRequest" form. <conference_center> stands for the organizations name registered with Live Meeting. <version> is the placeholder of the version number of the Live Meeting service API schema. An example of <version> is 4.0.

  2. The Live Meeting service replies with a URL pointing to the physical address of the conference centers API processor. All message requests must be sent to this URL when the API is used. The returned URL is known as the posting URL for your conference center. It is different from the URL used in the Live Meeting Web user interface. The posting URL should be obtained at the beginning of each application session.

  3. Send a request message to the conference center. Requests are sent in the following ways:

    • All XML request messages are sent using the HTTPS POST method.

    • For mass transfer requests, download requests are sent using the HTTPS GET method. Upload requests are sent using the HTTPS POST method.

  4. Parse the response returned from the conference center. The following responses are possible:

    • Responses to XML requests are in XML. For example, the CreateMeetingRequest element gets the CreateMeetingReply element.

    • Responses to mass transfer requests are byte streams that can be redirected to another process or saved to a local data store.

See Also

Concepts

Message Passing

GetPostingURL Message