Re: [Dev] Do we need to check active subscriptions/bookmarks etc.. before changing LC state from published to X
So there will be no way to delete an asset if there is even a single subscriber ? That's not useful. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Do we need to check active subscriptions/bookmarks etc.. before changing LC state from published to X
Hi Manu, I think we have similar behavior in API Manager also. Lets take our connector store as an example. Assume I have bookmark/subscribe (or even purchase) a connector. What if publisher suddenly took off the connector from the store. Isn't it bit confusing? We can block new subscriptions while giving access to existing subscribers IMO. On Wed, Aug 5, 2015 at 10:07 PM, Manuranga Perera m...@wso2.com wrote: So there will be no way to delete an asset if there is even a single subscriber ? That's not useful. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Do we need to check active subscriptions/bookmarks etc.. before changing LC state from published to X
Its even more wrong if I as a subscriber can prevent an asset from deleting, isn't it? ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Do we need to check active subscriptions/bookmarks etc.. before changing LC state from published to X
The ability to restrict new subscriptions is useful But I don't think we have to cover that in this release. ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Do we need to check active subscriptions/bookmarks etc.. before changing LC state from published to X
sent from my nexus4, ignore any typos On Aug 5, 2015 22:32, Manuranga Perera m...@wso2.com wrote: Its even more wrong if I as a subscriber can prevent an asset from deleting, isn't it? Technically yes. But what about ux? ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Do we need to check active subscriptions/bookmarks etc.. before changing LC state from published to X
Hi All, IMO we need to provide forceful delete option for relevant user levels(for admin). In that case all subscribed users need to get an notification from store. from UX perspective this is bit doubtful situation. In certain scenarios we can't allow to have forceful delete option. ex If subscriber with paid subscription we can't allow to have forceful action with the middle of subscription period. IMO we can't cater for all possible scenarios. so we need to choose how we are going to support within generic use cases. Regards, *Dakshika Jayathilaka* PMC Member Committer of Apache Stratos Senior Software Engineer WSO2, Inc. lean.enterprise.middleware 0771100911 On Wed, Aug 5, 2015 at 10:40 PM, Udara Rathnayake uda...@wso2.com wrote: sent from my nexus4, ignore any typos On Aug 5, 2015 22:32, Manuranga Perera m...@wso2.com wrote: Its even more wrong if I as a subscriber can prevent an asset from deleting, isn't it? Technically yes. But what about ux? ___ 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
