Actually, if you combine the 1.2 Auth component with the newly-
rewritten ACL component, you can scale to pretty much any level of
permissions complexity you want without very much trouble.  The items
you mentioned are well within the scope of it's capability.

On Mar 28, 9:20 pm, "Seb" <[EMAIL PROTECTED]> wrote:
> I haven't looked at the 1.2 component throughly enough, but as far as
> I know, no components support this;
>
> groups
> permissions
> users
> group_permissions
> user_permissions
>
> and because you don't want to define 150 000 permissions, you need url
> based (/admin/users/*) permissions and itemized
> (published_revised_article) permissions.
>
> As for Nate's idea,
> Here's a model;
> We're working on this;http://www.mydr.com.au/v2/physical_diagram_(draft).png
> (note the 'draft' status!)
> I'm fine with adapting it and generalizing it a bit more (ie,
> replacing enums by properly modeled tables).
> But then if you think that could become an interesting 'starting
> point', I could have a chat with the business and contribute it back
> if we get help from a few dev. I believe this could be a fair
> agreement. The business has agreed to fund and allocate resources to
> rebuild the site, work quoted to between 225 000 and 350 000$ by
> outsourcing companies, and so this will go forward.
>
> Any feed back welcome!
>
> Seb.
>
> On Mar 29, 5:00 am, "digital spaghetti"<[EMAIL PROTECTED]> wrote:
> > Another point I forgot to make is I see a lot of people re-inventing
> > the wheel.  How many different Auth components are there out there
> > (not to mention the official one in 1.2) for example.  [...]
>
> > Tane


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Cake 
PHP" group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/cake-php?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to