Hi Samisa, Please find my comments inline.
On Mon, Jan 6, 2014 at 10:52 AM, Samisa Abeysinghe <[email protected]> wrote: > > > On Mon, Jan 6, 2014 at 10:28 AM, Eranda Sooriyabandara <[email protected]>wrote: > >> Hi all, >> Now we exposed the all types of registries (will be Repository in future) >> to the outside registry kernel (Carbon kernel) via RegistryService. >> Here are the types of registries we have. >> > systemRegistry >> configSystemRegistry >> governanceSystemRegistry >> userRegistry >> configUserRegistry >> governanceUserRegistry >> > Here we have two major types of registries user registries and system registries. User registries are user specific registries and contain user details like username, user tenant and user realm and must use in the user activities. Permissions set for the user will be applied for all operations performed when using these registries. System registries are system level registries which only should use for saving system level metadata. In each of system or user registry there are four types. - registry - This has the fully access from the root level of the registry "/" - config registry - Registry for config space. This only has the access to config collection "/_system/config/" - governance registry - Registry for governance space. This only has the access to governance collection "/_system/governance/" - local registry - Registry for local space. This only has the access to local collection "/_system/local/" > Can you please explain what each of the above does? > >> >> But if we take a close look we should be only exposing >> configUserRegistry, governanceUserRegistry which actually should be use in >> the platform level components. Other than that if we need to save something >> to local registry or as systemRegistry we should specifically give methods >> for them. For example if we want to retrieve last indexed time of a server >> we need to have a separate method. >> >> There are several advantages over this modification. >> 1. No one allowed to modify local registry + we may not need to show that >> in the resource browser. >> 2. There can be security issues when we expose system registries over an >> API >> 3. We have used systemRegistries all over our components for some >> operations which is incorrect because its overriding the authorization >> model + people won't find the correct logs. >> 4. People can use the system registry in their custom handlers which we >> should not allowed >> > > It sounds as if, we are going to "re-factor" what we have in C5. Should we > not rather have a fresh look and "re-design" this to get the story right? > In other words, how about disregarding what we have and have a holistic new > look! > We are currently working on a refactoring plan, where we refactor the registry API, making it repository API of the carbon. As this is our basement of the registry if we go for a new holistic look we have to change everything in the registry model. If we go for it better we start discuss now since we may no longer continue on refactoring. thanks Eranda > >> WDYT? >> >> thanks >> Eranda >> >> >> -- >> >> *Eranda Sooriyabandara *Senior Software Engineer; >> Integration Technologies Team; >> WSO2 Inc.; http://wso2.com >> Lean . Enterprise . Middleware >> >> E-mail: eranda AT wso2.com >> Mobile: +94 716 472 816 >> Linked-In: http://www.linkedin.com/in/erandasooriyabandara >> Blog: http://emsooriyabandara.blogspot.com/ >> >> >> >> >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- *Eranda Sooriyabandara*Senior Software Engineer; Integration Technologies Team; WSO2 Inc.; http://wso2.com Lean . Enterprise . Middleware E-mail: eranda AT wso2.com Mobile: +94 716 472 816 Linked-In: http://www.linkedin.com/in/erandasooriyabandara Blog: http://emsooriyabandara.blogspot.com/
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
