addressalign-toparrow-leftarrow-rightbackbellblockcalendarcameraccwchatcheckchevron-downchevron-leftchevron-rightchevron-small-downchevron-small-leftchevron-small-rightchevron-small-upchevron-upcircle-with-checkcircle-with-crosscircle-with-pluscrossdots-three-verticaleditemptyheartexporteye-with-lineeyefacebookfolderfullheartglobegmailgoogleimageimagesinstagramlinklocation-pinmagnifying-glassmailminusmoremuplabelShape 3 + Rectangle 1outlookpersonplusprice-ribbonImported LayersImported LayersImported Layersshieldstartickettrashtriangle-downtriangle-uptwitteruseryahoo

Montana Programmers Message Board Montana Programmers Discussion Forum › User permissions using state machines

User permissions using state machines

Rob L.
Bozeman, MT
Post #: 18
I just read this post and thought it was kind of interesting. Has anybody ever used a state machine for user permissions instead of a whole pile of Boolean columns? Do you think this is overkill for most apps?

Booleans Are Baaaaaaaaaad

I'd be interested in hearing everybody's thoughts on trying something like this.

A former member
Post #: 3
I've used it, though in backbone.js instead of Ruby. I think that an app of any size should be storing its data in a model, and its generally easy to implement the state machine there. "Columns of booleans" sounds badly broken... if that is what you have you might look at ACL (access control lists). IMO those are broken too, but they will do the job and are generally available for "free" (they come bundled with most frameworks)
Powered by mvnForum

Our Sponsors

Sign up

Meetup members, Log in

By clicking "Sign up" or "Sign up using Facebook", you confirm that you accept our Terms of Service & Privacy Policy