Hi All, This is to update on the discussion carried out in [1].
In terms of resources, it was noted that both queue and topic have similar actions, hence to capture both these resources as a single resource called 'destination'. (Since internally, a queue is used to create a topic) Resource:Destination 1. create : create a queue 2. delete : remove queue 3. browse : view messages in a queue 4. purge : remove messages in a queue 5. publish: publish to a queue 6. subscribe : subscribe to a queue 7. view : view queue details. These queue details could include subscriptions made to a given queue. 8. close : close subscriptions of a queue 9. unsubscribe When considering a DLC (Dead Letter Channel) queue, there are two additional actions as below.Since DLC is also a queue, these actions will also be mapped to a 'destination' resource. 10. restore: Send the messages from DLC back to the original queue. 11. reroute: Send the messages from DLC to the original/different queue. Initial permission allocation will be given, where an admin user will create a role with a permission such as 'createQueue' for a given space ( wildcard based space such as topic.sports.* ), and the user who has this role assigned, can perform specified actions of that permission, on the queue/topic he/she creates. A subscription will not be captured as a separate resource since the actions related to a subscription are already mapped to queue actions(view, wwnershipclose, unsubscribe). In addition to above, ownership transfer of a resource will be possible for an admin user. [1] MB 4 - Permission Model Discussion Thanks, Himasha
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
