- From: Michael B Allen <ioplex@gmail.com>
- Date: Fri, 3 Oct 2014 15:27:14 -0400
- To: David Morris <dwm@xpasc.com>
- Cc: ietf-http-wg@w3.org
- Message-ID: <CAGMFw4gN0hN9NhKQG09f-HW2aEu9meUe4A8UF0XxJmxqhcU-wQ@mail.gmail.com>
On Fri, Oct 3, 2014 at 2:06 PM, David Morris <dwm@xpasc.com> wrote: > > I don't see any difference here between multiple TCP > connections and multiple streams within a single HTTP/2 > TCP connection. Ok. Then the server auth module just needs a unique id for that stream. So is there an HTTP/2 header that uniquely identifies the stream? If not, I think there should be one. And it should be generic like "Stream-ID" (as opposed to "Auth-ID"). Of course this all assumes that clients will use streams like they currently use TCP connections. Meaning only one multi-legged auth per stream. And clients would have to minimize and reuse the set of Stream-IDs they use. Mike
Received on Friday, 3 October 2014 19:27:41 UTC