Hi,

I'm currently having the admin part of one of my apps accessible by pure
username and password + role management checking.

I was planning to add namespaces for it. Then I came accross this (a bit
old but still...):
http://glu.ttono.us/articles/2006/08/30/guide-things-you-shouldnt-be-doing-in-rails

"Putting Controllers in Namespaces

This is really more trouble than it’s worth. You run into all sorts of
crazy errors if you do this and you’ll be confused and frustrated.
You’ll then ask other people about it and they’ll either blow you off
for using namespaces with controllers or procede to get confused and
frustrated as well. Then you’ll say, “I with I had listened to Kevin and
Chris”. If you want /admin/some_controller as an URL that’s fine. Use
the routing that’s built into rails."

I've used namespaces for admin before and actually it can create
confusion. On the other hand using a common controller with some extra
is_admin? checks can be a bit ugly. I know it all depends on how
different the admin funcionality is.

But is there any opinions/experiences you could share on this issue?

Thanks.
-- 
Posted via http://www.ruby-forum.com/.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Talk" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to