title: Does HTTP/2 multiplexing violate REST API rules?
body: <p>Multiplexing is a pretty cool feature of http/2. It allows using one connection to serve multiple requests from a single client simultaneously.</p>
  <p>My question is: does this multiplexing feature violate REST API rules?</p>
  <ol>
  <li>I understand that REST API enforces request-response architecture, but multiplexing without server-push (streaming) feature enabled is essentially one request -&gt; one response paradigm, so that's not a violation, is that right?</li>
  <li>REST API also enforces stateless, and I'm lost there: is multiplexing through a single connection considered as stateful or stateless?</li>
  </ol>
  <p>If I want to upgrade a REST API which is currently implemented with HTTP/1.1 to use HTTP/2, do I have the privilege to use the multiplexing feature, or I have to do stream after stream (req1, res1, req2, res2...)?</p>