On Mon, Aug 13, 2012 at 11:14 AM, Sumedha Rubasinghe <[email protected]>wrote:
> > > On Mon, Aug 13, 2012 at 10:26 AM, Subash Chaturanga <[email protected]>wrote: > >> >> >> On Mon, Aug 13, 2012 at 5:45 AM, Sumedha Rubasinghe <[email protected]>wrote: >> >>> In a nutshell, we store the tier selected as part of user's subscription >>> record. So even if you change the tier @ API level, that change does not >>> propagate to the subscriber unless you update the subscription with new >>> tier details. >>> >> Hi Sumedha, >> I tried to do similar kind of thing. But there was no such. WDYM updating >> the subscription ? The only option there is to resubscribe. Still the >> application bounded is not available there. >> > > I was referring to removing ur subscription from the application. > >> >> >>> >>> However, if you change a value in an existing tier, (eg: changing max >>> request count) this gets picked up without having to update the >>> subscription. >>> >>> >>> >>> On Mon, Aug 13, 2012 at 12:08 AM, Hiranya Jayathilaka >>> <[email protected]>wrote: >>> >>>> It's not natural for the API provider to change a tier of an API all >>>> the sudden, without the consent of the subscribers. Tier is a contract >>>> between the API provider and the subscriber. Subscriber chooses a tier at >>>> the point of subscription, after carefully reviewing it. The provider is >>>> supposed to keep supporting that. However if it must be done here are your >>>> options: >>> >>> >> Hi Hiranya, >> Yes, the subscriber chooses the tier at the point of subscription. But >> [1] - When provider changes the tier value, the value of the tier at >> subscriber end gets updated. >> So if this is the expected behavior, [1] is a bug and we should not allow >> the publisher to change the tier or provide some alternative.. Because that >> particular tier has dependent subscribers. >> >> AFAIC this not a bug. But more of a mutual understanding. If a provider > decides to change it's SLA on a tier, propagating that is not a problem. > Yes I agree. It's a more of a common sense issue. I don't see why anybody would want to change a tier for which customers have already subscribed. However if somebody really wants to do that, he need to go through a bit of trouble to make that happen. Thanks, Hiranya > > >> I think $subject is a possible use case a publisher may come across. As >> API-M provides API versioning capability it is not good to have multiple >> tiers per API at API creation. >> Hence, a possible suggestion is, we can recommend the publishers/subs, if >> they need $subject, you should go for a new version of the API with the >> changes and may be deprecate the previous. In that context, we can make the >> tier type *not* editable for publisher. >> WDYT ? >> > > Multiple tiers are there to introduce different SLAs (and pricing plans). > When publishing an API, publisher selects under what categories his API > will be exposed @. And when subscribing, subscribers decide what is the > service level they expect/budget and the decide on the tier to subscribe to. > > > > > >> >> >>> >>>> 1. Change the tier definitions by editing the tiers.xml in registry >>>> 2. Update the subscription entry in API Manager DB >>>> >>>> Thanks, >>>> Hiranya >>>> >>>> On Sun, Aug 12, 2012 at 11:02 PM, Subash Chaturanga >>>> <[email protected]>wrote: >>>> >>>>> Hi all, >>>>> I just noticed $subject in 1.0.0 release. Once I change the tier type >>>>> of my API from Bronze to Silver I could still send only one request per >>>>> minute. >>>>> More than one requests, it gives the same old throttled out response. >>>>> Same applies when transform from Silver to Gold. Is this a known issue ? >>>>> To change the tier type, I did that from publisher edit tab and saved, >>>>> is there anything more to be done for that to be effective ? >>>>> >>>>> >>>>> Thanks >>>>> -- >>>>> >>>>> Subash Chaturanga >>>>> Software Engineer >>>>> WSO2 Inc. http://wso2.com >>>>> >>>>> email - [email protected] >>>>> phone - 077 2225922 >>>>> >>>>> >>>>> _______________________________________________ >>>>> Dev mailing list >>>>> [email protected] >>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>> >>>>> >>>> >>>> >>>> -- >>>> Hiranya Jayathilaka >>>> Senior Technical Lead; >>>> WSO2 Inc.; http://wso2.org >>>> E-mail: [email protected]; Mobile: +94 77 633 3491 >>>> Blog: http://techfeast-hiranya.blogspot.com >>>> >>>> _______________________________________________ >>>> Dev mailing list >>>> [email protected] >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> >>> -- >>> /sumedha >>> +94 773017743 >>> >> >> >> >> -- >> >> Subash Chaturanga >> Software Engineer >> WSO2 Inc. http://wso2.com >> >> email - [email protected] >> phone - 077 2225922 >> >> > > > -- > /sumedha > +94 773017743 > -- Hiranya Jayathilaka Senior Technical Lead; WSO2 Inc.; http://wso2.org E-mail: [email protected]; Mobile: +94 77 633 3491 Blog: http://techfeast-hiranya.blogspot.com
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
