cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Manikanta Kattamuri <manikanta.kattam...@sungard.com>
Subject Re: [DISCUSS]De-coupling Account Services and User services.
Date Thu, 07 Feb 2013 08:20:03 GMT
On Thu, Feb 7, 2013 at 1:27 PM, Rohit Yadav <bhaisaab@apache.org> wrote:

> On Thu, Feb 7, 2013 at 12:27 PM, Manikanta Kattamuri
> <manikanta.kattamuri@sungard.com> wrote:
> > Hi All,
> >
> > Presently Account Services and Account Manager classes are responsible
> for
> > all the user operations like create, login, edit/update, change password,
> > lock user etc..
> >
> > What i am thinking of is to create a new UserService in Utils and move
> the
> > user methods in AccountServices to it and follow the same with
> > AccountManager and its implementation.
>
> utils should only have reusable utilities, interfaces which are
> contracts to be used among components should be in api if we want them
> to be generally available for all components including plugins.
>
> my mistake i was supposed to write it in 'api' where AccountService class
resides.


> >
> > So all the call for the user objects will be done through either
> > UserServices or UserManager classes.
> >
> > Advantages of it would be that we can create plugins just to integrate
> ACS
> > with third party AD services for user mgmt.
>
> To solve this problem, one way would be to define the UserServices
> interface (or whatever you want to introduce, I would still want the
> existing interface to be fixed and reused) and in your plugin make it
> depend on cloud-api, and your plugin's managerimpls can make use of
> this interface to do work.
>
> The present interfaces will be reused but the user related stuff will move
to new interface UserService.


> Regards.
>
> >
> > Any thoughts on this.
> >
> > --Mani
>
> --Mani

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message