That would take care of ACL related code. What would be the case with User Mgmt and Account Mgmt, can this be seperated to two different Classes/Services.
Manikanta. On Thu, Dec 20, 2012 at 1:32 PM, Likitha Shetty <[email protected]>wrote: > Manikanta, > > Check out this FS for API refactoring, > https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+API+refactoring > . > You will find that one of the items is to move ACL code (access checks and > roles) from the Service layer i.e. AccountManagerImpl to the API layer. > > Thank you, > Likitha > > -----Original Message----- > From: Manikanta Kattamuri [mailto:[email protected]] > Sent: Thursday, December 20, 2012 1:17 PM > To: [email protected] > Subject: Untangaling User Mgmt, Account Mgmt and ACL checking from > AccountManagerImpl. > > Hi, > > The current AccountManagerImpl sure takes care of a huge number of tasks > related to UserMgmt( Create, delete, login, user queries) > AccountMgmt(create, enable, disable, etc) and ACL(checkaccess and roles). > Is anyone working on re-factoring and untangling this piece of code area? > > > Manikanta. > >
