On Thu, Apr 10, 2014 at 6:24 AM, Sumedha Rubasinghe <[email protected]>wrote:

> Dinusha,
> Let's schedule a discussion today with Azeez, Shankar & Prabath.
>
sent a calender invitation @2-3pm.

>
>
> On Thu, Apr 10, 2014 at 6:18 AM, Dinusha Senanayaka <[email protected]>wrote:
>
>> Hi,
>>
>> We have identified following ares to be cover with $subject. Additionally
>> we need to define  features that could be useful for users, like assets
>> sharing across tenants etc. Thoughts ?
>>
>>
>>
>> Data Isolation
>>
>> Execution Isolation
>>
>> Publisher
>>
>>    -
>>
>>    Assets need to saved in to correct tenant space.
>>    -
>>
>>       Save into tenant registry (Comes with ES)
>>       -
>>
>>       Save into AppM DB (Need to check whether artifacts get saved with
>>       tenant ID)
>>       -
>>
>>    Need to check resources associated with asset get saved in correct
>>    tenant registry space (Resources like Documents)
>>
>>
>>
>>    -
>>
>>    When publishing, synapse config  need to deploy in correct tenant
>>    space.
>>    -
>>
>>    Application publish workflow extension handling for tenant.
>>
>> Store
>>
>>    -
>>
>>    Logged in user should see only the assets published by his tenant
>>    domain (Comes with ES)
>>    -
>>
>>       Need to check associated resource loading (Documents)
>>       -
>>
>>       Recently added assets, tags
>>       -
>>
>>    Subscription handling
>>
>>
>>
>> Gateway
>>
>>
>>    -
>>
>>    Tenant aware invocations.
>>    -
>>
>>       SSO handling (currently cookie saved in cache)
>>
>>
>>
>>
>> Regards,
>> Dinusha.
>>
>> --
>> Dinusha Dilrukshi
>> Senior Software Engineer
>> WSO2 Inc.: http://wso2.com/
>> Mobile: +94725255071
>> Blog: http://dinushasblog.blogspot.com/
>>
>
>
>
> --
> /sumedha
> b :  bit.ly/sumedha
>



-- 
Dinusha Dilrukshi
Senior Software Engineer
WSO2 Inc.: http://wso2.com/
Mobile: +94725255071
Blog: http://dinushasblog.blogspot.com/
_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Reply via email to