Hi Caleb,
On Aug 10, 2011, at 12:22 PM, 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.
WDYT?
I need some more information before giving an opinion.
Same as Sergiu I'd like some explanations as to where this would be used. Does it mean
all page content writers will need to manually call $doc.dropPermissions() whenever they
want to make their document "secure"? That seems very cumbersome and we can be
sure people won't do that.
So what use cases does this solve?
Thanks
-Vincent
Caleb