From 7c17b58eec102b8a97908cc8a62432a8adcb5db2 Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Thu, 4 Jun 2015 22:43:36 +0200 Subject: [PATCH] LIBCURL-STRUCTS: clarify for multiplexing --- docs/LIBCURL-STRUCTS | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/docs/LIBCURL-STRUCTS b/docs/LIBCURL-STRUCTS index 136d17ce7fe030..11dee85398b395 100644 --- a/docs/LIBCURL-STRUCTS +++ b/docs/LIBCURL-STRUCTS @@ -52,6 +52,9 @@ for older and later versions as things don't change drastically that often. The libcurl source code generally use the name 'data' for the variable that points to the SessionHandle. + When doing multiplexed HTTP/2 transfers, each SessionHandle is associated + with an individual stream, sharing the same connectdata struct. Multiplexing + makes it even more important to keep things associated with the right thing! 1.2 connectdata @@ -70,7 +73,7 @@ for older and later versions as things don't change drastically that often. connection or the SessionHandle. Functions in libcurl will assume that connectdata->data points to the - SessionHandle that uses this connection. + SessionHandle that uses this connection (for the moment). As a special complexity, some protocols supported by libcurl require a special disconnect procedure that is more than just shutting down the