Would it be possible to change Roles to work more like Users?
It would be far easier to manage if the /slide/roles/[role] could be managed by adding a collection with the same name as the user you want to add to that role, i.e. /slide/roles/root/root and /slide/roles/root/Ollie would put root and Ollie in the root role, or /slide/roles/user/john and /slide/roles/user/tom to be members of the user role and so forth. The current method of fetching the member list property, appending the new user and proppatch'ng it back is cumbersome and error prone. It would be cleaner and easier to use and easier to program with the client library if the mechanism was the same as adding a user with mkcol to the /slide/users/ collection, yes?
These are fundamentally different ideas, and trying to unify them won't work: groups and roles are NOT the same. Slide already has major problems with roles, as evidenced by the fact that role membership can be represented as a property (role membership should not be enumerable!).
I agree that groups are far easier to manage than roles - and I see this as a compelling reason to, whenever possible, avoid any use of roles. Personally, I'd deprecate them entirely.
Just an opinion from someone who has spent too much time fighting role/group semantic mismatches...
Mike
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
