aboutsummaryrefslogtreecommitdiff
path: root/lib/README.http2
diff options
context:
space:
mode:
authorDaniel Stenberg <daniel@haxx.se>2013-09-07 11:12:12 +0200
committerDaniel Stenberg <daniel@haxx.se>2013-09-07 11:28:12 +0200
commit61672bde441cf67c1250a9a66f902700d9d95ed4 (patch)
tree42f487218c31dff08fc1be5758ed6dab361c0a91 /lib/README.http2
parent13dbb41c4991bdd87768e0d3b6d3398cb1869676 (diff)
README.http2: how to use it best with the multi API?
Diffstat (limited to 'lib/README.http2')
-rw-r--r--lib/README.http25
1 files changed, 5 insertions, 0 deletions
diff --git a/lib/README.http2 b/lib/README.http2
index 4d54c0c69..40f6a650e 100644
--- a/lib/README.http2
+++ b/lib/README.http2
@@ -17,3 +17,8 @@ HTTP2 with libcurl
(or NPN) to negotiate which protocol to continue with. Possibly introduce an
option that will cause libcurl to fail if not possible to use http2.
+To consider:
+
+ - How to tell libcurl when using the multi interface that all or some of the
+ handles are allowed to re-use the same physical connection. Can we just
+ re-use existing pipelining logic?