With this functionality there is a key difference that gets introduced. For API & Application level throttling, subscriber can choose the throttling policy he is going to subscribe into.
But for API resource level throttling, subscriber cannot control the throttling limits. He has to adhere to whatever configured by the API publisher for resource contexts. If you visit https://code.google.com/apis/console, this concept is also in compliance with what is being done there. On Tue, Jul 16, 2013 at 2:01 PM, Sanjeewa Malalgoda <[email protected]>wrote: > Hi All, > We are going to add Throttling Support at API Resource Level. Here is a > brief description on what we are going to do here. > > Current functionality: > Now we do have throttling support at API level and application level. > Consumer can select throttling tier for API when they subscribe to API, > also they can define throttling tier when they create > application(application is bundle of APIs). > > New Addition: > Support for providing throttling tier support for resource level and HTTP > verb level. > > Throttling tiers per resource and http verb level can be define when we > create API like we add throttling tiers per API. So when subscribers going > to subscribe to API they will notify throttling limits at resource level. > see following sample. > > > API - testAPI (allow subscribers to select gold and unlimited). > /testAPI/1.0.0/. Subscribers can select this when they subscribe to API > |---Resource - student/ > |--get - Bronze (define when we create api and subscribers cannot > change this. But they will notify limits). > |--put -Silver (define when we create api and subscribers cannot > change this.But they will notify limits). > |--delete - Bronze(define when we create api and subscribers > cannot change this.But they will notify limits). > > > Our plan is to add this resource section of API create UI. > > So API publishers can select throttling tier when they create API and add > resource level permissions to API. > > Implementation: > Throttling key for this scenario will contain access_token + api +resource > + http_verb combination. Throttling values once loaded will be cached for > performance. Sample UI for this implementation attached. > > Thanks, > Sanjeewa. > > -- > * > * > *Sanjeewa Malalgoda* > WSO2 Inc. > Mobile : +94713068779 > > <http://sanjeewamalalgoda.blogspot.com/>blog > :http://sanjeewamalalgoda.blogspot.com/<http://sanjeewamalalgoda.blogspot.com/> > > > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- /sumedha b : bit.ly/sumedha
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
