I think your articles should implement the Resource_Interface and your users
should implement the Role_Interface. The article/resource will have
knowlnedge about who its creator is and since both objects are passed to the
assertion you could then simple do something like:
if ($article->ownerId ==
Colin Guthrie-6 wrote:
>
> ([...] the Zend_Acl webinar PDF clearly states an example use of
> Asserts as:
> * Allow only the author to edit an article.
>
>
> But when I started thinking about it, I couldn't work out how to do this
> part of the validation. A singleton object knows the user d
]>
To:
Sent: Thursday, September 25, 2008 4:13 PM
Subject: [fw-general] Using ACL asserts to validate access to specific
instances of a generic resource
(resend - first one seemed to get eaten)
Hi,
I'm currently devising how best to deploy Zend_Acl in an application I'm
retrofittin
(resend - first one seemed to get eaten)
Hi,
I'm currently devising how best to deploy Zend_Acl in an application I'm
retrofitting to Zend Framework.
I've spend the time to read the docs and view the webinars and I came to
the conclusion that implementing Zend_Acl_Assert_Interface is the
correc
