Search

The purpose of output protection is to increase content protection during transmission between a computer’s video or audio output port and the input port of another device such as a monitor or set of speakers (output). This is useful to prevent someone from intercepting copy protected content “en route” between such devices, known commonly as an "analog hole".

Output Protection is specialized stuff and so this post will be a bit arcane to most, but will hopefully be useful to a few folks out there who are familiar with OP and want to integrate it into their Silverlight apps.

This application is more of an example of what is possible with Silverlight and DotNetNuke rather than it is a practical application. Instead of just showing traffic to the page, the gauges could show more relevant data such as total orders placed, or the number of help desk tickets (there are plans to use this in a future version of http://ADefHelpDesk.com).

Before I start, I just want to mention that this is a very old "flame war". On the official Silverlight Forums, there was a thread that went on and on, becoming quite ugly with various ad-hominem attacks, and it eventually got so ugly that --thankfully -- the moderators took the whole thread down. However, not being averse to controversy, I of course had my say there and was duly accused by various characters of being arrogant, an idiot, and what not. My position then was exactly as it remains now; basically, Microsoft is not going to give you native synchronous web requests in Silverlight because there is too much room for abuse by developers who will freeze the UI Thread, the browser then locks up, and of course Microsoft gets blamed for a "crappy product".