I would really appreciate a concrete use case on this. I'm struggling to figure out a scenario where someone would monetize the number of frames of an application. WebSockets are usually used for server side push events.
We have a number of high priority items to deliver which are critical to the market we want to win. Unless there is a clear demand and clear use-case for this, it's hard to justify deprioritization of such a feature for WS monetization over frames. So it would be really helpful if you can describe the business need for this or even show an existing example of such. On Fri, Sep 25, 2020 at 12:35 PM Vanjikumaran Sivajothy <va...@wso2.com> wrote: > @Nuwan Dias <nuw...@wso2.com> @Arshardh Ifthikar <arsha...@wso2.com>, > Any comment on this and plan to adopt into the product? > > On Tue, Sep 8, 2020 at 11:42 AM Vanjikumaran Sivajothy <va...@wso2.com> > wrote: > >> @Nuwan Dias <nuw...@wso2.com> there are multiple opportunities there for >> the API producers who use the WebSocket as their protocol. >> Few examples I see; >> 1) Gaming API >> 2) Documentation APIs >> >> On Sat, Sep 5, 2020 at 5:41 AM Nuwan Dias <nuw...@wso2.com> wrote: >> >>> Monetizing websocket APIs for data bandwidth usage would make sense. But >>> why would one want to set a price per frame? >>> >>> On Sat, Sep 5, 2020 at 5:57 PM Vanjikumaran Sivajothy <va...@wso2.com> >>> wrote: >>> >>>> Since the Product has a nessary component to put this together, Can you >>>> consider this in upcoming version and implement it? >>>> >>>> On Tue, Sep 1, 2020 at 10:41 PM Arshardh Ifthikar <arsha...@wso2.com> >>>> wrote: >>>> >>>>> Yes, events are published to analytics per frame >>>>> >>>>> On Wed, Sep 2, 2020 at 11:08 AM Fazlan Nazeem <fazl...@wso2.com> >>>>> wrote: >>>>> >>>>>> AFAIK we publish an event to Analytics Server per incoming WebSocket >>>>>> frame. This can be verified by a simple test. >>>>>> >>>>>> On Wed, Sep 2, 2020 at 10:53 AM Silmy Hasan <si...@wso2.com> wrote: >>>>>> >>>>>>> Hi vanjikumaran, >>>>>>> >>>>>>> We make use of analytics to summarize and persist the request count >>>>>>> for a certain period of time for an API, as we need an internal storage >>>>>>> to >>>>>>> persist the request counts in order to publish it to the Billing engine >>>>>>> time to time . So If the data(Request stream) is published to analytics >>>>>>> per >>>>>>> frame for websocket APIs , achieving this should not be a problem. I >>>>>>> think >>>>>>> for web socket APIs, request stream is published for each frame and if >>>>>>> so >>>>>>> the same peristing and publishing logic could be used for websocket >>>>>>> apis >>>>>>> and this should be a minimal effort. if not we should find a way to >>>>>>> internally persist the frame count for webscoket APIs and write the >>>>>>> logic >>>>>>> and publish it to the billing engine. >>>>>>> @Fazlan Nazeem <fazl...@wso2.com> @Rukshan Premathunga >>>>>>> <ruks...@wso2.com> @Arshardh Ifthikar <arsha...@wso2.com> please >>>>>>> confirm whether streams are published to analytics per frame for >>>>>>> Websocket >>>>>>> APIS. >>>>>>> >>>>>>> Also we have had discussions on whether frame or bandwidth based >>>>>>> pricing fits web socket apis better. So I think we can check the >>>>>>> feasibility of implementing it bandwidth wise as well and decide on the >>>>>>> better option >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Tue, Sep 1, 2020 at 9:45 AM Vanjikumaran Sivajothy < >>>>>>> va...@wso2.com> wrote: >>>>>>> >>>>>>>> Any update on this? >>>>>>>> >>>>>>>> On Tue, Aug 25, 2020 at 7:10 PM Vanjikumaran Sivajothy < >>>>>>>> va...@wso2.com> wrote: >>>>>>>> >>>>>>>>> Hi Team, >>>>>>>>> >>>>>>>>> WSO2 API Manager offers a monetization functionality in the >>>>>>>>> product and It is working perfectly with HTTP Request-Response for the >>>>>>>>> dynamic pricing. However, WebSocket endpoints do not work like a >>>>>>>>> typical >>>>>>>>> HTTP request-Response as once the connection is made the >>>>>>>>> communication happens via frames. >>>>>>>>> >>>>>>>>> Therefore, It is ideal to consider to implement the dynamic >>>>>>>>> pricing option for frame count rather than request count. >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> https://github.com/wso2/product-apim/issues/9185 >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> >>>>>>>>> *Vanjikumaran Sivajothy | Solution Engineer |WSO2 Inc. (m) +1 925 >>>>>>>>> 464 6816 | (e) vanji AT wso2.com <http://wso2.com>* >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> >>>>>>>> *Vanjikumaran Sivajothy | Solution Engineer |WSO2 Inc. (m) +1 925 >>>>>>>> 464 6816 | (e) vanji AT wso2.com <http://wso2.com>* >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Shilmy Hasan >>>>>>> Software Engineer | WSO2 >>>>>>> >>>>>>> E-mail :si...@wso2.com >>>>>>> Phone :0779188653 >>>>>>> web : http://www.wso2.com >>>>>>> >>>>>>> [image: https://wso2.com/signature] <https://wso2.com/signature> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Thanks & Regards, >>>>>> >>>>>> *Fazlan Nazeem | *Associate Technical Lead | WSO2 Inc >>>>>> Mobile : +94772338839 | fazl...@wso2.com >>>>>> >>>>>> >>>>>> >>>>> >>>>> -- >>>>> *Arshardh Ifthikar* >>>>> Senior Software Engineer | WSO2 Inc. >>>>> >>>>> Email: arsha...@wso2.com >>>>> Mobile: +94777218551 >>>>> Web: http://wso2.com >>>>> >>>>> <http://wso2.com/signature> >>>>> >>>> >>>> >>>> -- >>>> >>>> *Vanjikumaran Sivajothy | Solution Engineer |WSO2 Inc. (m) +1 925 464 >>>> 6816 | (e) vanji AT wso2.com <http://wso2.com>* >>>> >>>> >>>> _______________________________________________ >>>> Dev mailing list >>>> d...@wso2.org >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>> >>> >>> -- >>> *Nuwan Dias* | VP and deputy CTO - API Management and Integration | >>> WSO2 Inc. >>> (m) +94 777 775 729 | (e) nuw...@wso2.com >>> >> >> >> -- >> >> *Vanjikumaran Sivajothy | Solution Engineer |WSO2 Inc. (m) +1 925 464 >> 6816 | (e) vanji AT wso2.com <http://wso2.com>* >> >> >> > > -- > > *Vanjikumaran Sivajothy | Solution Engineer |WSO2 Inc. (m) +1 925 464 6816 > | (e) vanji AT wso2.com <http://wso2.com>* > > > -- *Nuwan Dias* | VP and deputy CTO - API Management and Integration | WSO2 Inc. (m) +94 777 775 729 | (e) nuw...@wso2.com
_______________________________________________ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
