Hi Bhathiya, Please find my answers in line.
On Thu, Apr 6, 2017 at 1:27 PM, Bhathiya Jayasekara <[email protected]> wrote: > Hi Pubudu, > > A few minor questions to understand how this works exactly. > > 1) Let's say publisher publishes a "public" API. Then, a notification will > be added to the topic. Does this notification has label information so that > "private" gateways can ignore it? > This suggestion came during the discussions and we have thought of including that. Label information will be available in the notification message. Gateway will filter the notifications. This will prevent gateway trying to pull the APIs when there is a notification. > 2) Let's say we introduce a gateway with a new label. Now do we have an UI > in publisher to assign existing APIs to this new label, or do we have to > update each API individually? Former would give a better user experience. > Basically when you are adding a new API, you need to select one or more labels for the API. Now this is available in the UI. When you introduce a new label, same as before you need to update the API with the new label from the UI. By default, if you haven't selected any label at the API creation time, default label will be added to the API. > 3) I believe there will be a service in the Core to register new label so > that gateways can use. Is that how it works? > Yes, there will be a service to register labels in the core. Gateways will use this. Thank you! -- *Pubudu Gunatilaka* Committer and PMC Member - Apache Stratos Software Engineer WSO2, Inc.: http://wso2.com mobile : +94774078049 <%2B94772207163>
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
