Hi
Does anybody have recommendations on how to organize operations for
Rhino.Security? I'm creating a system where we need to lock down
access to various domain entities, reports, other tasks like importing/
exporting, sending emails, batch calculation operations, and
workflows. Since these operations need to be setup in the database
where the permissions can be given to users and user groups, I'm
hoping to create a database admin tool to insert these operations when
I build a new database.
Should I just have a bunch of constants defined somewhere for all of
the different opreations ("/Entity/Employee/EditSSN", "/Import/Sales/
Inventory", "/Workflow/TimeSheet/Overtime/Approval") or perhaps a
resource file? Or should I define an interface on the Entity, Import
service and Workflow service classes that defines the operations, or
perhaps add attributes to the various entities and use reflection to
then get the correct text string for each operation?
I know I could do any of these, but I'm wondering what others have
done in the past and if there are any recommendations.
Thanks
Dan
--
You received this message because you are subscribed to the Google Groups
"Rhino Tools Dev" group.
To post to this group, send email to rhino-tools-...@googlegroups.com.
To unsubscribe from this group, send email to
rhino-tools-dev+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/rhino-tools-dev?hl=en.
