|
|
In addition to the unicast and multicast logging capabilities included with Windows Media Services, the logURL attribute enables each clientData element to direct logging information to other locations on the network. By using the logURL attribute within a clientData element, usage information about the elements contained within the clientData element is sent by the client to a logging program that either displays the data, integrates it into a database, or saves it as a file. Logging data is sent once for each address specified in the logURL attribute.
The logURL attribute is particularly useful if you require logging data for individual elements in a playlist or if you want to send relevant data about specific elements in the playlist directly to the content providers. If you are working with an advertising partner that wants real-time data about the clients that receive their advertisements, you can provide that information by using the logURL attribute. The log data sent using the logURL attribute can be received and interpreted by the multicast logging program Wmsiislog.dll. This means that any computer configured to receive multicast logs can receive data from the logURL attribute.
Client log data varies depending on the logURL attribute's parent element. In the following example, log data is sent to a network location running Showlog.asp when the client first opens the playlist and to a different network location running Wmsiislog.dll when the client plays the media element Example01.wmv.
<?wsx version='1.0'?>
<smil>
<clientData logURL="http://webserver1/log/showlog.asp"/>
<media src="Example01.wmv">
<clientData logURL="http://webserver2/data/wmsiislog.dll"/>
</media>
<media src="Example02.wmv"/>
</smil>
The logURL attribute can be specified for the following playlist element:
Notes