On Fri, 25 Jan 2008 23:31:44 +0100, Close, Tyler J. <[EMAIL PROTECTED]> wrote:
Why is this situtation "very unusual"? It may be common. Say I've got a secure mashup application that manages an ATOM store. Since it's secure, the browser cache may be emptied after every visit, so the check requests will have to be repeated on each use.

What is the scenario where you delete/create/modify a lot of different resources in an Atom store at once?

I agree that distinct URIs makes sense, but I can't really imagine a scenario where this will be a problem. And given that all existing policies support per-resource and doing it per-resource is the most secure (in case one forgotton application is not yet updated or so) I rather stick with the current design.


--
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>

Reply via email to