4 ms·

Making a request to the server is completely different than opening a new connection. HTTP/2 lets you use an already opened connection, if applicable. Thus it i

Making a request to the server is completely different than opening a new connection. HTTP/2 lets you use an already opened connection, if applicable. Thus it is able to bypass making a handshake/etc. for every request made as well. Making a request however will still have to traverse the network irregardless. GraphQL gives you a query language to tell the server what you want in a single request. So if it is your first request to server, and a new connection needs to be opened, HTTP/2 is irrelevant. Basically, HTTP/2 and GraphQL have NOTHING to do with each other.

drew-y 7y ago
That's not the point I was trying to make. I agree they are essentially unrelated. But they do both try to reduce requests made. From the article: > Not only that, but HTTP/2 has a new concept called Server Push. Without going into too much detail, server push allows servers to preemptively send responses before the client requests them.
ClumsyPilot 7y ago
Even in Http 1.1 you can keep the connection open, you dont need to re-negotiate tls and friends for every request. https://en.m.wikipedia.org/wiki/HTTP_persistent_connection https://en.m.wikipedia.org/wiki/HTTP_persistent_connection