Hi, I have few questions related to this..Please find them inline below..
On Tue, Jul 30, 2013 at 12:15 AM, Sumedha Rubasinghe <[email protected]>wrote: > This discussion happened as part of *Enterprise Store* discussion. > Participants: Nuwan, Azeez, Sanjiva, Srinath, NuwanD, Lalaji, Sanjeewa, > Sumedha > > *Current Functionality:* > 1. At the point of publishing an API, publisher can select the visibility > scope (one of Globally visible, selected tenants, tenant only > [private/public]). > 2. Based on selected scope, APIs will be created with correct set of > permission indicators in WSO2 Governance Registry > 3. @ the point of populating a store, based on the store type APIs will be > fetched from tenant registries > > *Limitations in this approach:* > 1. Assumption of single registry for all tenants (fetching, publishing > criteria fails with tenant partitioning) > 2. High computational cost for populating global tenant store (also known > as super tenant store) > 3. API publishing is only supported for WSO2 API Store type > 4. Tight coupling with WSO2 API Store semantics for API publishing & > fetching > > *New Approach:* > 1. At the point of publishing an API, it can also be published to multiple > (external) stores > > I would like to know how the visibility scope applies with this approach. Does the existing visibility scopes will be available with new approach too..If so how the mappings would be like? For example how the 'Public' visibility scope define.. > 2. These stores will be defined through configuration (run time > registration can be considered for future work, limited by lack of standard > API for publishing API) > > 3. APIs will published to external stores through their APIs. This has > several design considerations: > - Any API store can be integrated to WSO2 API Publisher through this > approach > - WSO2 API Store will also be treated as an external one > - Concept of Super Tenant Store will no longer be applicable *** > - If an API is shared with another tenant store, it will be stored in that > tenant's storage (if sharing is removed, relevant removal should follow) > > 4. *** When navigated to http://<IP/Domain>/store (formally known as > Super tenant's store), it will show a list of tenant store URLs only > With current Store implementation,are we going to show tenant store URLs for anonymous view as well..? And even a user logged to /Store and if he has a tenant store URL with him,if he is not from that specific tenant,he cannot login to tenant Store and continue further processing.So if we show as above,the only use-case is users can browse the APIs from tenant stores.. And additionally,with this approach the 'Public' visibility scope of tenants' APIs not getting useful,as there's no view of 'Public' Store for tenants with this approach and only 'Tenant Store' view will available.. > 5. This concept should be supported in WSO2 Generic Store as well > > Feedback welcome. > Thanks; > > -- > /sumedha > b : bit.ly/sumedha > -- Lalaji Sureshika WSO2, Inc.; http://wso2.com/ email: [email protected]; cell: +94 71 608 6811 blog: http://lalajisureshika.blogspot.com
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
