MetaService 1.2 : Creating a client

In essence a Soap service, such as the Cwc MetaService, is a web service to which a client has to POST a specifically formatted HTTP Header and XML message, to in turn retrieve XML containing the data a client is after. To implement a client that consumes the MetaService, it would therefore suffice to manually craft the request message, post it to the service and deserialize the XML response.


However, it's often much more convenient to use code generating tools that are built into IDE's, part of your platform, or exist as standalone applications. We have tested various platforms and IDEs against the MetaService, and all make implementing a client trivial.

Check the links below for sample code and some discussion about ways to consume the MetaService with different platfoms. Please note that in most cases these were created without deep knowledge of the actual platform, so better solutions may exist. In all cases sample code is provided for demo purposes only, they are not production ready.


this is a .NET 2.0 command line utility written in C#. It allows customers and partners to download every aspect of archived webcasts and potentially make them available offline while maintaining full functionality. It's included as a sample here as it's a Meta Service client and comes with Creative Commons licensed source code.

Important note:
Do not create a browser based client (Flash, Silverlight, Java Applet) that contains your Webcast Management System username and password. If you are looking to implement something like this, please request a new account specifically for the MetaService from , and consider these new account details available to anyone with access to your application.
The recommended way of creating an in-browser application is to create a server sided proxy to the MetaService, and have that pass on data to a browser client.