Can you create document explaining this feature in detail with possible user scenarios. It would be great if we can have some test artifacts as well.
Thanks, sanjeewa. On Thu, Dec 20, 2018 at 3:38 PM Varuni Punchihewa <[email protected]> wrote: > Hi Sanjeewa, > > There's no effect to ballerina filters from setting the http version to > 2.0. But the connection established via the client and the microgateway and > microgateway with the backend would be more efficient and fast due to the > features like header compression, it's full multiplexed nature etc. > Furthermore, we won't be using the server push feature in the microgateway > since there's no much use cases of it with the microgateway. > > Thank you > Best Regards, > > *Varuni Punchihewa* > Intern - Software Engineering | *WSO2* > *Tel:* +94 71 699 5861 > <http://wso2.com/signature> > > > On Fri, Oct 26, 2018 at 12:05 PM Sanjeewa Malalgoda <[email protected]> > wrote: > >> Can you please explain how are we planning to go ahead with this feature? >> Even now with ballerina we can create http2 client endpoint or server >> endpoint with http2 follows. >> If we do same now how will it work with existing filters? >> >> endpoint http:Listener testEP { >> port: 9095, >> httpVersion: "2.0" >> }; >> >> Thanks, >> sanjeewa. >> >> On Sat, Oct 6, 2018 at 5:13 PM Varuni Punchihewa <[email protected]> >> wrote: >> >>> Hi all! >>> Please find my project description and the design as below. >>> >>> *Project description* >>> >>> The WSO2 API Microgateway currently supports only http and https as the >>> incoming and outgoing transport protocols. This project is for enabling it >>> to support HTTP2 for both incoming and outgoing message flows. We need to >>> evaluate the use of OAuth2.0, and rate limiting capabilities on the current >>> Microgateway and see how this impacts the move to HTTP2. >>> >>> *Solution Design* >>> >>> - Supporting the messages received by the microgateway from the >>> clients, by both HTTP/1.1 and HTTP/2.0 protocols >>> - All the communication that happen between the Microgateway and the >>> Back end service will support HTTP/2.0 (The maximum version supported is >>> set to 2.0. In case if it supports only 1.1, then it will be backward >>> compatible to 1.1 and would not be a problem to communications) >>> >>> Best Regards, >>> >>> *Varuni Punchihewa* >>> Intern - Software Engineering | *WSO2* >>> >>> *Tel:* +94 71 699 5861 >>> _______________________________________________ >>> Architecture mailing list >>> [email protected] >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >> >> >> -- >> *Sanjeewa Malalgoda* >> Software Architect | Associate Director, Engineering - WSO2 Inc. >> (m) +94 712933253 | (e) [email protected] | (b) Blogger >> <http://sanjeewamalalgoda.blogspot.com>, Medium >> <https://medium.com/@sanjeewa190> >> >> GET INTEGRATION AGILE <https://wso2.com/signature> >> Integration Agility for Digitally Driven Business >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> > -- *Sanjeewa Malalgoda* Software Architect | Associate Director, Engineering - WSO2 Inc. (m) +94 712933253 | (e) [email protected] | (b) Blogger <http://sanjeewamalalgoda.blogspot.com>, Medium <https://medium.com/@sanjeewa190> GET INTEGRATION AGILE <https://wso2.com/signature> Integration Agility for Digitally Driven Business
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
