[x]
Posted via EE Mobile

Search, ask, and monitor your questions on the go with EE Mobile. Visit Experts Exchange from your mobile device and never be out of touch again.

Question
[x]
Attachment Details
[x]
The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

  • The Grade of the Solution
  • The Zone Rank of the Expert Providing the Solution
  • The Number of Author and Expert Comments
  • The Number of Experts Contributing
  • The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

8.2

Best implementation for Role Based Access Control in Ruby on Rails

Asked by smetterd in RubyOnRails, Ruby Scripting Language

I would like to learn to implement role-based access control on my growing apps. In former days, I would create a db field for users with a string like 0000101111101100011111, where each place holder was given a 'role'. Then in my app I would see whether or not the account had that permission switched on (in other words, character #5 means "isInstructor") and grant an action accordingly.

As the app grows, however, that becomes cumbersome.... Not very DRY either.

I've notices in larger professional apps that developers use separate tables.... a users table, a roles table, and a permissions table. This makes more sense.

What is the best practice in Rails??

Something like this?
http://wiki.rubyonrails.org/rails/pages/AccessControlListExample

Thank you!
[+][-]02/20/08 06:20 AM, ID: 20937926Accepted Solution

View this solution now by starting your 30-day free trial. Setting up your free trial is quick, easy, and secure. We will return you to this solution, unlocked, when you're done.

About this solution

Zones: RubyOnRails, Ruby Scripting Language
Sign Up Now!
Solution Provided By: dberner9
Participating Experts: 2
Solution Grade: A
 
[+][-]02/25/08 09:26 PM, ID: 20981835Assisted Solution

Assisted solutions are selected by the member who asked the question as a comment that contributed to their question's solution.

Start your 30-day free trial to view this Assisted Solution or ask the Experts your question.

 
 
Loading Advertisement...
20091111-EE-VQP-92 / EE_QW_2_20070628