Hey Ryan,
It seems like your system is simple enough that an ACL would not even
be required. Where it *would* come in handy is if you created a
situation where users could join groups, and create/edit blog posts
collectively.
But if you only have a single direct relationship between posts and
very true, and in all reality i'm just doing a 'beta' version of my web
app initially, and i'll probably use a simpler authentication schema,
but as the Cake ACL documentation isn't extremely extensive (definitely
useful, and totally digestible) I was wondering what would be the best
The general rule of thumb about ACO's are that you want to create one
for each object that you want to control access to, and arrange them
hierarchically such that there are as few links between the ARO and ACO
trees as necessary.
--~--~-~--~~~---~--~~
You
would it be bad form to mix ACL with a specific access check - to go
back to the blog example, which I know is a bit too simple to be
appropriate, but - would it be wrong to set say all children of the
'members' ARO group had 'read' access to the blogs ACO group, adn then
check if the logged in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
In an application not at all like a blog, I do both, as (to keep with
your blog example) not all of my user's are allowed to modify their own
blog posts, but I still need to determine whether a blog post belongs to
the current user in order to
