W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2010

Re: [widgets] WARP default policy

From: Robin Berjon <robin@berjon.com>
Date: Wed, 5 May 2010 11:40:16 +0200
Cc: public-webapps WG <public-webapps@w3.org>
Message-Id: <34FB85E4-1F54-4005-8D76-C72FFD50CB13@berjon.com>
To: Scott Wilson <scott.bradley.wilson@gmail.com>
On May 4, 2010, at 19:29 , Scott Wilson wrote:
> I've just been reading through the WARP spec again, and in particular this stood out:
> 
> In the default policy, a user agent must deny access to network resources external to the widget by default, whether this access is requested through APIs (e.g. XMLHttpRequest) or through markup (e.g. iframe, script, img).
> 
> I'm not sure if this statement is actually helpful here. While it makes sense that WARP defines policies that widen access beyond whatever the UA's default policy may be, is it strictly necessary to define the default policy? 

Well, if you think about it a little bit further, is it really necessary to have a way of defining a network access policy, and if so is the content you're distributing the best place to do so? I personally have a somewhat reserved judgement about whether WARP is useful at all. A rather large number of people expressed this requirement, so it was delivered, and it's quite possible that they were right. But it's also possible that they're not which is why I'm happy that it's not part of P+C.

If you noticed this because you're working on it for Wookie, I'm not sure that's it's worth the (minimal) effort. WARP makes no sense in a Web context.

-- 
Robin Berjon - http://berjon.com/
Received on Wednesday, 5 May 2010 09:40:48 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:38 GMT