Hi, Although The Hypertext Transfer Protocol (HTTP) is a wildly successful protocol, there are some drawbacks in HTTP/1.0 and HTTP/1.1 versions. Overhead of headers and one request at a time are some of them. So, HTTP/2 has been introduced and it enables a more efficient use of network resources and a reduced perception of latency by introducing header field compression and allowing multiple concurrent exchanges on the same connection. It also introduces unsolicited push of representations from servers to clients.
When we consider the use cases we can identify 4 possible communication scenarios according to the following diagram. They are 1. Communication between HTTP2 supporting client and HTTP2 supporting backend server 2. Communication between HTTP2 supporting client and HTTP2 not supporting backend server 3. Communication between HTTP2 not supporting client and HTTP2 supporting backend server 4. Communication between HTTP2 not supporting client and HTTP2 not supporting backend server The proposed Architecture : 1. Implementing an a Inbound Endpoint which supports HTTP2 for communication with the client. 2. Implementing Connector to provide HTTP2 specifications for communication between ESB and back-end servers. Thanks, -- Chanaka Balasooriya, *Software Engineer Intern* *WSO2, Inc. :http://wso2.com <http://wso2.com>* *Mobile:+9471 2947 898*
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
