Hi all, This is WRT, #1725 on Redmine.
+++++++++++++++++++++ The idea is to create a special role that gives READ, WRITE, DELETE and AUTHORIZE access to a particular asset making it possible for a particular user or set of users take ownership of it. This thought came up during a WSO2 Store Milestone Planning Meeting, and mimics the functionality of Google Docs. +++++++++++++++++++++ Before going ahead with this, we have a few things to get clarified. 1. How would this role be named? This shouldn't be the name of the Asset itself, because there can be multiple assets by the same name. It even cant be name + namespace (or similar prefix/postfix), because there can be assets that differ by version. So, what's the best way to name it? 2. How should we be displaying this role in the management console? Should it show up just like any other role, or is there some special treatment in the Registry Browser? Since the role and the asset are 1-to-1, we shouldn't be displaying such roles against other assets, which makes it require some special treatment. 3. Is it just one such role or more? For instance, G-Docs has three types of privileges when it comes to sharing (i.e. View, Edit, Owner). Appreciate some quick responses on these in order to make it possible for us to ship this with G-Reg 4.6.0, making it available for WSO2 Store etc. Thanks, Senaka. -- * <http://us13.wso2con.com/> * * * *Senaka Fernando* Senior Technical Lead; WSO2 Inc.; http://wso2.com* Member; Apache Software Foundation; http://apache.org E-mail: senaka AT wso2.com **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 Linked-In: http://linkedin.com/in/senakafernando *Lean . Enterprise . Middleware
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
