It depends on your needs. In my case, I needed a robust / yet fine grained
system that could start small ( with roles restrictions), and grow as the
complexity of the changing business rules needed it to. I chose ActiveRBAC
for that project, because it allows me to manage access by role, permission,
or group, and I can protect the entire app, a controller, an action, or a
menu selection, as needed.
If your needs are simpler, you might want the experience of creating your
own, are borrowing examples from Rails Recipes, AWDwR. As with many things,
there is no "one size fits all". Though Ruby on Rails fits many
things
very well.
-Larry
On 8/2/06, Alex Moore <alex@prohost.com.au> wrote:>
> Hey,
>
>
>
> Would you guys recommend just coding your own authentication and ACL
> system, or is it best just to use one of acts_as_authenticated,
> LoginGenerator and alike. There''s a good example in Rails
Recipies and
> Agile Web Development with Rails 2nd Edition that I can base it on also.
>
>
>
> What would you suggest.... and why?
>
>
>
>
>
>
>
> _______________________________________________
> Rails mailing list
> Rails@lists.rubyonrails.org
> http://lists.rubyonrails.org/mailman/listinfo/rails
>
>
>
--
Best Regards,
-Larry
"Work, work, work...there is no satisfactory alternative."
--- E.Taft Benson
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://wrath.rubyonrails.org/pipermail/rails/attachments/20060803/4fecdbf0/attachment.html