Hi Varuni, I think in the first phase we have to build the http2 to http scenario. Basically if a back-end service is offering an http service, we can create an http2 receiving API on the microgateway. This way we build a mechanism of providing http2 support on a http service.
Thanks, NuwanD. On Mon, Sep 24, 2018 at 3:33 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* > > - Forwarding the messages received by the microgateway from the > clients, over HTTP/1.1 protocol to HTTP/2.0 protocol > - When it comes to the transport layer between the microgateway and > the back-end service, give an option to select http1 or http2 (in the > command line), in order to use the server push promises facility offered by > http2, if the back-end supports http2. If it does not, then it will be > using the http1 protocol. > - If the back-end supports http2, then the Microgateway will fetch all > the promises received from the back-end (it will check whether there's any > promises via hasPromise() first), construct the requested resource, and > send it to the Client. > > > > Best Regards, > > *Varuni Punchihewa* > Intern - Software Engineering | *WSO2* > > *Tel:* +94 71 699 5861 > -- *Nuwan Dias* | Director | WSO2 Inc. (m) +94 777 775 729 | (e) [email protected] [image: Signature.jpg]
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
