Is there any infrastructure in place for specifying which users are allowed to perform which actions?
I think it would be useful to be able to add users - who cannot subscribe themselves to calendars - who can read, but not write (some) calendars The former could be implemented by - allowing `superusers' to specify roles for users - allowing `superusers' to add calendars to other users - adding something like Wasp/Swarm or perhaps wicket-auth-roles to enforce those rules The latter by - allowing `superusers' to modify other users' calendars - adding a 'readonly' flag to calendars which only superusers can modify (eventually I can imagine the CalendarUser relation might have to become a many-to-many, in that case I suppose the 'readonly' flag should be on the CalendarUser relation instead of on the Calendar) Arnout --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "webical-developers" 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/webical-developers?hl=en -~----------~----~----~----~------~----~------~--~---
