Hi Manoj,
On Tue, Feb 11, 2014 at 10:16 PM, Manoj Fernando <[email protected]> wrote: > Not a nice user experience to be throttled out whilst using a web app for > sure. :( It just don't sell well as compared to throttling back-end APIs > and services which has obvious benefits. > > But if you really have to do it, my suggestion is to use URL patterns as a > unique identifier for throttle contexts. By default, you can configure the > throttle to allow all resources unless specified as throttle configuration > objects. So for web resources like CSS, images, etc... it will not > throttle, but the moment you create a resource hungry data grid for > example... you can create a throttle configuration specifying the URI as an > identifier. > +1, Thats the plan for this phase. > > Regards, > Manoj > > > > > On Tue, Feb 11, 2014 at 2:36 PM, Sanjeewa Malalgoda <[email protected]>wrote: > >> >> >> >> On Mon, Feb 10, 2014 at 6:58 PM, Venura Kahawala <[email protected]> wrote: >> >>> Hi, >>> >>> As you may be already aware 'App manager' is capable of providing a >>> gateway for web applications. Web Apps can be registered in the publisher >>> and can be published to the store so the users can subscribe and consume >>> web applications. >>> >>> Currently we are in the stage of implementing throttling for the >>> gateway. This is a bit different from API Manager since, consumer/ client >>> of the web application is not capable of sending a unique identifier to the >>> gateway (In AM this unique identifier is OAuth token which is given for a >>> client application). This is because, client should be able to type the >>> gateway URL in the browser and access the web app. >>> >>> We need to identify the client who is calling the gateway and throttle >>> based on the client. >>> >>> Any ideas on this are most welcome. >>> >> >> Normally when we throttle out web applications and services we might >> consider bandwidth passed through wire(incoming, out going). So we can >> consider some context registered and request bandwidth comes for that >> context( Also if we need to measure bandwidth we can do that inside >> handler). We used similar concept for web apps deployed in stratos. If we >> are planning to do request count based throttling mechanism we might need >> to consider consider web app context(we can derive this from request url) >> and session cookie combination as throttle key. But IMO when it come to web >> application, request count based throttling doesn't make much sense. >> >> Thanks, >> sanjeewa. >> >>> >>> Regards, >>> Venura >>> >>> -- >>> Senior Software Engineer >>> >>> Mobile: +94 71 82 300 20 >>> >>> >>> _______________________________________________ >>> Architecture mailing list >>> [email protected] >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >>> >> >> >> -- >> >> *Sanjeewa Malalgoda* >> Senior Software Engineer >> 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 >> >> > > > -- > Manoj Fernando > Director - Solutions Architecture > > Contact: > LK - +94 112 145345 > Mob: +94 773 759340 > www.wso2.com > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Senior Software Engineer Mobile: +94 71 82 300 20
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
