Is the server-side file required, or for testing purposes only?

Sep 1, 2009 at 6:54 PM

In the instructions, re: component 4:

4.) Server side components ( Unzip on a web server and create a virtual directory pointing to the unzipped structure.

We're trying to determine whether this ZIP file is strictly necessary on the server.  From the "The sample player page has a simple text box to add stream URL..." text at the end of the instructions, it seems like the & SamplePlayer.html are there to facillitate inputting a mulitcast stream's URL into the local player so it can begin streaming?

e.g., we have our own multicast windows-media streaming server that will be publishing the streams, and we're attempting to play these streams on OSX clients.  Is installing Silverlight + the starlight plugin on the OSX client sufficient, or are the server-side components still necessary?  If they are, it's not clear how the streaming software on the server would know that the components in /bin/release are even there and would call upon these libraries?

Thanks for any detail/clarification you can offer!

Sep 1, 2009 at 6:58 PM

Silverlight is a browser plugin, not a standalone client.  The server side components are just a web page that hosts a Silverlight application which can play multicast streams.  Does that clarify the role of this component?

Sep 1, 2009 at 7:07 PM

sorry, not really ... I'm not clear the "web page that hosts a Silverlight application" part; e.g., by the "Silverlight application," are you referring to the app on the server that actually sends out out the multicast windows media stream?  ...and by "hosts," do you mean that the server components ZIP files are merely a window for the client to be able to input the URL for a stream, or does it contain actual libraries that the server uses for streaming content?

On the silverlight multicast announcement page, there are a couple of points that claim that no server changes are necessary to allow a silverlight client to playback a multicast WMS stream, e.g.:

  • Leverages the existing Windows Media Services (WMS) multicast infrastructure broadly deployed among Enterprises – no server or network changes required
  • Requires the install of a single ActiveX or NPAPI plug-in to the user’s desktop


Sep 1, 2009 at 7:23 PM

The content is streamed by your existing WMS infrastructure.  The issue is that Silverlight is not a standalone application, but must run in a web browser.  The web browser must fetch a page from somewhere, so you need to put a web page on a web server somewhere.  The web page is in the, along with a compiled Silverlight XAP package that the web page references.  The Silverlight XAP will execute on the client machine inside the user's web browser.