On 08/10/2011 06:22 AM, Caleb James DeLisle wrote:
> Right now we have dropPermissions which makes a specific guarantee, there
> will not be any programming
> right for the duration of the request cycle.
>
> Sometimes a user might want to drop permissions for the duration of the
> document rendering.
> This would mean {{include}} macros, $doc.getRenderedContent() would allow
> permissions to be gained back
> while the included document was being rendered and after the content of that
> document is finished
> rendering, the permissions would be returned.
>
> I think it would do more harm than good to break the promise that
> dropPermissions() makes so I propose
> adding $doc.dropPermissions() to do this.
>
> I think $doc.dropPermissions() vs. $context.dropPermissions() is intuitive
> and easily explained but if
> anyone has another suggestion for a name, I'd be glad to hear it.
Can you give me a better example, when would doc.dropPermission be
needed and context.dropPermission is too much? How would you get back
rights? And how do you prevent the supposedly sandboxed code from using
the same mechanism to get back the rights?
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
_______________________________________________
devs mailing list
[email protected]
http://lists.xwiki.org/mailman/listinfo/devs
