This will be used by several products. Hence I think we need to have it in a common repo such as carbon-commons or something. Sameera any thoughts on this?
On Tue, Apr 7, 2015 at 9:46 AM, Chanaka Fernando <[email protected]> wrote: > Hi Sanjeewa, > > AFAIR we haven't modified throttle code(dependency 3.3.0-wso2v2 and core > 4.2.1) for long time and we are using it as it is. > We may use the same component version as its already available on repos. > If we need to do any development or fix/improve anything we may need to > get it to git with other version and continue. > WDYT? > > I think it would be better if we get this code to git and maintain it > there. That will allow us to develop/fix the code in the future. > > @Sagara: Once we have the API-Everywhere story implemented, we can use the > API Manager level throttling for other products as well. We are currently > implementing an improved throttle mediator by using the existing throttle > core implementation. That is the reason we need this code to be taken in to > Git repository. > > AFAIK, in either case, it would be better to have this code in the Git > repository. > > WDYT? > > Thanks, > Chanaka > > > On Mon, Apr 6, 2015 at 5:31 PM, Sagara Gunathunga <[email protected]> wrote: > >> >> >> On Mon, Apr 6, 2015 at 5:03 PM, Chanaka Fernando <[email protected]> >> wrote: >> >>> Hi All, >>> >>> With the latest refactoring of carbon platform source, throttling core >>> implementation has been removed from the platform. But inside APIM and ESB, >>> we need this feature to be supported. AFAIU, even services deployed in AS >>> require this throttling capability. What would be the best way forward for >>> supporting throttling functionality at product level? >>> >> >> What we have removed is old implementation of throttling used with AS/ESB >> due to lot of issues, AFAIK APIM don't use this old implementation, APIM >> already have new throttling implementation. Original plan was to enable >> APIM throttling implementation to AS/DSS/ESB through API- Everywhere. >> >> Thanks ! >> >>> >>> >>> Thanks, >>> Chanaka >>> >>> -- >>> -- >>> Chanaka Fernando >>> Technical Lead >>> WSO2, Inc.; http://wso2.com >>> lean.enterprise.middleware >>> >>> mobile: +94 773337238 >>> Blog : http://soatutorials.blogspot.com >>> LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0 >>> Twitter:https://twitter.com/chanakaudaya >>> Wordpress:http://chanakaudaya.wordpress.com >>> >>> >>> >>> >>> _______________________________________________ >>> Architecture mailing list >>> [email protected] >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >>> >> >> >> -- >> Sagara Gunathunga >> >> Senior Technical Lead; WSO2, Inc.; http://wso2.com >> V.P Apache Web Services; http://ws.apache.org/ >> Linkedin; http://www.linkedin.com/in/ssagara >> Blog ; http://ssagara.blogspot.com >> >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > -- > Chanaka Fernando > Technical Lead > WSO2, Inc.; http://wso2.com > lean.enterprise.middleware > > mobile: +94 773337238 > Blog : http://soatutorials.blogspot.com > LinkedIn:http://www.linkedin.com/pub/chanaka-fernando/19/a20/5b0 > Twitter:https://twitter.com/chanakaudaya > Wordpress:http://chanakaudaya.wordpress.com > > > > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Kasun Indrasiri Software Architect WSO2, Inc.; http://wso2.com lean.enterprise.middleware cell: +94 77 556 5206 Blog : http://kasunpanorama.blogspot.com/
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
