Hi Jeremy, I am working on implementing role-based authorization with sequel (along with warden). I have a sketch here:
https://github.com/jamiehodge/sinatra-warden-roles The sketch is currently using a yaml file. I would like to move over to a solution that forgoes serialization and uses a more natural chaining of the subsets. It should also support limiting fields for updates. I am struggling to decide where the responsibility for this control lies. I was hoping that you be willing to share some insight into how to best use subsets and set_fields or set_only and whether this logic should lie in the model classes, in a separate module or somewhere else entirely. Thank you, once again. Jamie -- You received this message because you are subscribed to the Google Groups "sequel-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/sequel-talk?hl=en.
