Re: [Dev] [API Manager] - Status of API Subscriptions
Hi, Please find my comment inline, as we'll be doing a small amendment to this. On Fri, Aug 8, 2014 at 3:23 PM, Abimaran Kugathasan abima...@wso2.com wrote: Hi Sumedha, In Current APIM, following are the status of a API Subscriptions BLOCKED, PROD_ONLY_BLOCKED, UNBLOCKED, ON_HOLD, REJECTED Consider following scenario/use case and relevant status of API subscriptions 1. An Application subscribes an API - UNBLOCKED 2. Publisher blocks the Application- BLOCKED 3. Application unsubscribes the API - The entry will be removed from DB 4. Same Application subscribes to same API - UNBLOCKED (A new entry in the DB) In this case, the Application was blocked by the publisher. Since we have deleted the entry from DB, Application can invoke the API after re subscribing to the API With this implementation (keeping one status for API subscriptions), there can be multiple scenarios having same problem. So, we have to introduce two status for API subscription. 1. One for keeping the application state - SUBSCRIBE/UNSUBSCRIBE 2. Another for keeping publisher's action on the subscription - BLOCK/UNBLOCK/PROD_ONLY_BLOCKED With the introduction of these two status, please find the new status for the above use case. 1. An Application subscribes to an API - SUBSCRIBE,UNBLOCKED 2. Publisher blocks the Application- SUBSCRIBE,BLOCKED 3. Application unsubscribes the API - UNSUBSCRIBE,BLOCKED 4. Same Application subscribes to same API - SUBSCRIBE,BLOCKED So, even the application re subscribing to API, it can't invoke. Here we don't delete any subscription entries from DB. So we can find the history of the subscription of a API As discussed with Abimaran, in addition to UNBLOCKED, BLOCKED and PROD_ONLY_BLOCKED states, we have to consider ON_HOLD and REJECTED states also, when deleting entries from the subscriptions table. This is to prevent issues such as [1]. As an application unsubscribes, we'll delete the relevant subscription entry unless the subscription is in BLOCKED or PROD_ONLY_BLOCKED states. [1] https://wso2.org/jira/browse/APIMANAGER-2997 Thanks, Dilini -- Thanks Abimaran Kugathasan Software Engineer | WSO2 Inc Data APIs Technologies Team Mobile : +94 77 1708229 http://stackoverflow.com/users/515034 http://lk.linkedin.com/in/abimaran http://www.lkabimaran.blogspot.com/ https://github.com/abimaran https://twitter.com/abimaran ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- *Dilini Muthumala* Software Engineer, WSO2 Inc. *E-mail :* dil...@wso2.com *Mobile: *+94713 400 029 ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [API Manager] - Status of API Subscriptions
Hi Abimaran These new statuses is it for 171 version or is it for a specific client. We can cover these new statuses with the 171 pack in QA regards, Shavantha Weerasinghe Senior Software Engineer QA WSO2, Inc. lean.enterprise.middleware. http://wso2.com http://wso2.org Tel : 94 11 214 5345 Fax :94 11 2145300 On Fri, Aug 8, 2014 at 3:23 PM, Abimaran Kugathasan abima...@wso2.com wrote: Hi Sumedha, In Current APIM, following are the status of a API Subscriptions BLOCKED, PROD_ONLY_BLOCKED, UNBLOCKED, ON_HOLD, REJECTED Consider following scenario/use case and relevant status of API subscriptions 1. An Application subscribes an API - UNBLOCKED 2. Publisher blocks the Application- BLOCKED 3. Application unsubscribes the API - The entry will be removed from DB 4. Same Application subscribes to same API - UNBLOCKED (A new entry in the DB) In this case, the Application was blocked by the publisher. Since we have deleted the entry from DB, Application can invoke the API after re subscribing to the API With this implementation (keeping one status for API subscriptions), there can be multiple scenarios having same problem. So, we have to introduce two status for API subscription. 1. One for keeping the application state - SUBSCRIBE/UNSUBSCRIBE 2. Another for keeping publisher's action on the subscription - BLOCK/UNBLOCK/PROD_ONLY_BLOCKED With the introduction of these two status, please find the new status for the above use case. 1. An Application subscribes to an API - SUBSCRIBE,UNBLOCKED 2. Publisher blocks the Application- SUBSCRIBE,BLOCKED 3. Application unsubscribes the API - UNSUBSCRIBE,BLOCKED 4. Same Application subscribes to same API - SUBSCRIBE,BLOCKED So, even the application re subscribing to API, it can't invoke. Here we don't delete any subscription entries from DB. So we can find the history of the subscription of a API -- Thanks Abimaran Kugathasan Software Engineer | WSO2 Inc Data APIs Technologies Team Mobile : +94 77 1708229 http://stackoverflow.com/users/515034 http://lk.linkedin.com/in/abimaran http://www.lkabimaran.blogspot.com/ https://github.com/abimaran https://twitter.com/abimaran ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [API Manager] - Status of API Subscriptions
Hi Shavantha, It's for the product 1.7.1, not only for any specific clients. On Mon, Aug 18, 2014 at 8:55 AM, Shavantha Weerasinghe shavan...@wso2.com wrote: Hi Abimaran These new statuses is it for 171 version or is it for a specific client. We can cover these new statuses with the 171 pack in QA regards, Shavantha Weerasinghe Senior Software Engineer QA WSO2, Inc. lean.enterprise.middleware. http://wso2.com http://wso2.org Tel : 94 11 214 5345 Fax :94 11 2145300 On Fri, Aug 8, 2014 at 3:23 PM, Abimaran Kugathasan abima...@wso2.com wrote: Hi Sumedha, In Current APIM, following are the status of a API Subscriptions BLOCKED, PROD_ONLY_BLOCKED, UNBLOCKED, ON_HOLD, REJECTED Consider following scenario/use case and relevant status of API subscriptions 1. An Application subscribes an API - UNBLOCKED 2. Publisher blocks the Application- BLOCKED 3. Application unsubscribes the API - The entry will be removed from DB 4. Same Application subscribes to same API - UNBLOCKED (A new entry in the DB) In this case, the Application was blocked by the publisher. Since we have deleted the entry from DB, Application can invoke the API after re subscribing to the API With this implementation (keeping one status for API subscriptions), there can be multiple scenarios having same problem. So, we have to introduce two status for API subscription. 1. One for keeping the application state - SUBSCRIBE/UNSUBSCRIBE 2. Another for keeping publisher's action on the subscription - BLOCK/UNBLOCK/PROD_ONLY_BLOCKED With the introduction of these two status, please find the new status for the above use case. 1. An Application subscribes to an API - SUBSCRIBE,UNBLOCKED 2. Publisher blocks the Application- SUBSCRIBE,BLOCKED 3. Application unsubscribes the API - UNSUBSCRIBE,BLOCKED 4. Same Application subscribes to same API - SUBSCRIBE,BLOCKED So, even the application re subscribing to API, it can't invoke. Here we don't delete any subscription entries from DB. So we can find the history of the subscription of a API -- Thanks Abimaran Kugathasan Software Engineer | WSO2 Inc Data APIs Technologies Team Mobile : +94 77 1708229 http://stackoverflow.com/users/515034 http://lk.linkedin.com/in/abimaran http://www.lkabimaran.blogspot.com/ https://github.com/abimaran https://twitter.com/abimaran ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev -- Thanks Abimaran Kugathasan Software Engineer | WSO2 Inc Data APIs Technologies Team Mobile : +94 77 1708229 http://stackoverflow.com/users/515034 http://lk.linkedin.com/in/abimaran http://www.lkabimaran.blogspot.com/ https://github.com/abimaran https://twitter.com/abimaran ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [API Manager] - Status of API Subscriptions
Hi Sumedha, In Current APIM, following are the status of a API Subscriptions BLOCKED, PROD_ONLY_BLOCKED, UNBLOCKED, ON_HOLD, REJECTED Consider following scenario/use case and relevant status of API subscriptions 1. An Application subscribes an API - UNBLOCKED 2. Publisher blocks the Application- BLOCKED 3. Application unsubscribes the API - The entry will be removed from DB 4. Same Application subscribes to same API - UNBLOCKED (A new entry in the DB) In this case, the Application was blocked by the publisher. Since we have deleted the entry from DB, Application can invoke the API after re subscribing to the API With this implementation (keeping one status for API subscriptions), there can be multiple scenarios having same problem. So, we have to introduce two status for API subscription. 1. One for keeping the application state - SUBSCRIBE/UNSUBSCRIBE 2. Another for keeping publisher's action on the subscription - BLOCK/UNBLOCK/PROD_ONLY_BLOCKED With the introduction of these two status, please find the new status for the above use case. 1. An Application subscribes to an API - SUBSCRIBE,UNBLOCKED 2. Publisher blocks the Application- SUBSCRIBE,BLOCKED 3. Application unsubscribes the API - UNSUBSCRIBE,BLOCKED 4. Same Application subscribes to same API - SUBSCRIBE,BLOCKED So, even the application re subscribing to API, it can't invoke. Here we don't delete any subscription entries from DB. So we can find the history of the subscription of a API -- Thanks Abimaran Kugathasan Software Engineer | WSO2 Inc Data APIs Technologies Team Mobile : +94 77 1708229 http://stackoverflow.com/users/515034 http://lk.linkedin.com/in/abimaran http://www.lkabimaran.blogspot.com/ https://github.com/abimaran https://twitter.com/abimaran ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [API Manager] - Status of API Subscriptions
Appreciate your feedback on this. On Fri, Aug 8, 2014 at 3:23 PM, Abimaran Kugathasan abima...@wso2.com wrote: Hi Sumedha, In Current APIM, following are the status of a API Subscriptions BLOCKED, PROD_ONLY_BLOCKED, UNBLOCKED, ON_HOLD, REJECTED Consider following scenario/use case and relevant status of API subscriptions 1. An Application subscribes an API - UNBLOCKED 2. Publisher blocks the Application- BLOCKED 3. Application unsubscribes the API - The entry will be removed from DB 4. Same Application subscribes to same API - UNBLOCKED (A new entry in the DB) In this case, the Application was blocked by the publisher. Since we have deleted the entry from DB, Application can invoke the API after re subscribing to the API With this implementation (keeping one status for API subscriptions), there can be multiple scenarios having same problem. So, we have to introduce two status for API subscription. 1. One for keeping the application state - SUBSCRIBE/UNSUBSCRIBE 2. Another for keeping publisher's action on the subscription - BLOCK/UNBLOCK/PROD_ONLY_BLOCKED With the introduction of these two status, please find the new status for the above use case. 1. An Application subscribes to an API - SUBSCRIBE,UNBLOCKED 2. Publisher blocks the Application- SUBSCRIBE,BLOCKED 3. Application unsubscribes the API - UNSUBSCRIBE,BLOCKED 4. Same Application subscribes to same API - SUBSCRIBE,BLOCKED So, even the application re subscribing to API, it can't invoke. Here we don't delete any subscription entries from DB. So we can find the history of the subscription of a API -- Thanks Abimaran Kugathasan Software Engineer | WSO2 Inc Data APIs Technologies Team Mobile : +94 77 1708229 http://stackoverflow.com/users/515034 http://lk.linkedin.com/in/abimaran http://www.lkabimaran.blogspot.com/ https://github.com/abimaran https://twitter.com/abimaran -- Thanks Abimaran Kugathasan Software Engineer | WSO2 Inc Data APIs Technologies Team Mobile : +94 77 1708229 http://stackoverflow.com/users/515034 http://lk.linkedin.com/in/abimaran http://www.lkabimaran.blogspot.com/ https://github.com/abimaran https://twitter.com/abimaran ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
