What kind of possibilities does HTTP/2 bring to REST APIs?
I am particularly interested in the streams and multiplexing support. Streams allows response to be sent in multiple messages.
In cases where Response has huge body, or cases where every millisecond matters, server should be able to start sending response as soon as it has parts of it available, and then send rest of the response in subsequent messages.
I will appreciate if someone can share their thoughts about it. Have you implemented something like it in your APIs, Does it work.
Thanks,
Manoj
--
You received this message because you are subscribed to the Google Groups "API Craft" group.
To unsubscribe from this group and stop receiving emails from it, send an email to api-craft+...@googlegroups.com.
Visit this group at http://groups.google.com/group/api-craft.
For more options, visit https://groups.google.com/d/optout.
Resources pushing is exciting for media-types like HAL, I guess.
It'd probably make hypermedia caching more efficient.