Quote:
Originally Posted by Ravenheart
|
I haven't read all the detail yet but it seems to be a client side plugin. The idea being that a web site owner can specify a set of restrictions on the client side.
An example pertinent to this discussion could be...
A web site owner specifies that clients can only run javascript that is served from the same domain. In the case of the trials where javascript was inserted that made requests to dns.sysip.net, the web site owner could specifically say that the javascript was not allowed to run and the browser would obey that restriction.
At least that is what I am reading into that. I think it's a great idea, although for it to be of any use it really does need the major browser vendors to adopt it by default. Look at what happened to p3p, probably something that would be of interest to most of us here...
http://www.w3.org/P3P/. I'm not sure if the idea has been dropped entirely, but it appears to have stalled due to lack of support from the major browser vendors.
"After a successful Last Call, the P3P Working Group decided to publish the P3P 1.1 Specification as a Working Group Note to give P3P 1.1 a provisionally final state.
The P3P Specification Working Group took this step as there was insufficient support from current Browser implementers for the implementation of P3P 1.1."