[Grok-dev] grok.define_role

Jan-Wijbrand Kolman janwijbrand at gmail.com
Wed Jul 25 13:48:05 EDT 2007

On 7/25/07, Luciano Ramalho <luciano at ramalho.org> wrote:
> On 7/25/07, Jan-Wijbrand Kolman <janwijbrand at gmail.com> wrote:
> > I wonder if we want Grok to have something like:
> >
> >   grok.define_role('my.rolename', permissions=('my.editpermission',
> > 'my.whateverpermissions'))
> +1
> > Or would this tie Grok to much to the default Zope security policy?
> Making sensible defaults is in the spirit of agility, right? And the
> default Zope 3 security policy is sensible.
> For the developers of Rails, such choices are harder. Since they have
> no underlying framework like we do, the risk of boxing-in the end
> developer is greater for them.
> In Grok I think we can offer one preferred way without fear, because
> the end developer always has the option of going the Zope 3 way if
> more flexibility is needed.

I have a working prototype in my own application already. I can easily
port it to a grok branch for others to look at. I will do so tomorrow.

kind regards,

Jan-Wijbrand Kolman

More information about the Grok-dev mailing list