Thanks Sameera. On Mon, Oct 20, 2014 at 1:13 PM, Sameera Medagammaddegedara < [email protected]> wrote:
> Hi Kasun, > > This requirement was discussed lightly during a ES/UES review meeting > [1],however it was decided that this was not a pressing concern at the > time.A few of the immediate problems that were identified (not documented > in that mail thread): > > > 1. *Asset publishing concerns* > - How will assets be published to tenant stores? > - Option #1: Clone the assets in the tenant store > - The tenants API could be used to create and publish assets > in the super tenant as cloned assets > - This method would cause the asset owner to loose control > over the asset.Since the original asset owner may not be a tenant > user , > who has ownership of that asset? > - If the original asset is updated there will need to be a > mechanism to synch all cloned assets > - An asset in addition to its meta data will accumulate > dynamic data over the course of its life.This dynamic data will > include > user comments ,tags and ratings. > - How can this dynamic data be propagated back to the > original asset? > - Is it correct to propagate this dynamic data back to the > original asset? (Since each tenant will have a different user > set) > > I'm not sure whether this would scale for any of our store deployments in the cloud. Any thoughts? > > 1. > *Asset curation concerns * > - Asset visibility must be controlled on a per tenant basis > > > *Reference* > [1] [Meeting Minutes] Discussion to standardize UES/ES dependency > > Thank You, > Sameera > > On Sun, Oct 19, 2014 at 12:56 AM, Kasun Indrasiri <[email protected]> wrote: > >> Hi Ruchira/SameeraM, >> >> AFAIK, this is a common requirement for other products that uses ES (for >> instance API Store) capabilities. Do we have some design constrains on >> supporting this? >> >> On Fri, Oct 17, 2014 at 12:01 AM, Kasun Indrasiri <[email protected]> wrote: >> >>> This is a very important capability for our iPaaS work and I guess it >>> will be critical to API cloud etc. Do we have this capability already >>> available or will that be available in the upcoming ES release? >>> >>> On Thu, Oct 16, 2014 at 6:50 PM, Buddhima Wijeweera <[email protected]> >>> wrote: >>> >>>> Hi, >>>> >>>> Currently with ES, when a super-tenant upload items to the store, they >>>> are only visible to super-tenant users only. This will become a barrier >>>> when we create stores which can be accessed by different tenants. >>>> >>>> Therefore, we would appreciate if ES team can take this issue in to >>>> consideration, and provide a solution in a future release. >>>> >>>> Thanks! >>>> >>>> -- >>>> Buddhima Wijeweera >>>> Software Engineer; WSO2 Inc.; http://wso2.com , >>>> >>>> Email: [email protected] >>>> Blog: https://buddhimawijeweera.wordpress.com >>>> GitHub Profile: https://github.com/Buddhima >>>> >>>> _______________________________________________ >>>> Dev mailing list >>>> [email protected] >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> >>> -- >>> Kasun Indrasiri >>> Software Architect >>> WSO2, Inc.; http://wso2.com >>> lean.enterprise.middleware >>> >>> cell: +94 77 556 5206 >>> Blog : http://kasunpanorama.blogspot.com/ >>> >> >> >> >> -- >> Kasun Indrasiri >> Software Architect >> WSO2, Inc.; http://wso2.com >> lean.enterprise.middleware >> >> cell: +94 77 556 5206 >> Blog : http://kasunpanorama.blogspot.com/ >> > > > > -- > Sameera Medagammaddegedara > Software Engineer > > Contact: > Email: [email protected] > Mobile: + 94 077 255 3005 > -- Kasun Indrasiri Software Architect WSO2, Inc.; http://wso2.com lean.enterprise.middleware cell: +94 77 556 5206 Blog : http://kasunpanorama.blogspot.com/
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
