[wip] create pull interface
[refactor] do not allocate memory within flatten_headers
[wip] switch http1 protocol to prefer the pull interface
[wip][http2] flatten the arguments to socket write
initial buffer size should be selectable
Merge branch 'kazuho/expr/inbuf-initial-size' into kazuho/expr/pulling-generator
initial alloc size of http2 output buffer should be 80k
update the tests following the changes
Merge branch 'master' into kazuho/expr/pulling-generator
[refactor] `capacity` represents either minimum initial capacity or current capacity, `bytes` is now used to determine if the buffer is a prototype
Merge branch 'kazuho/expr/inbuf-initial-size' into kazuho/expr/pulling-generator
[http2] send at max the capacity of the output buffer
[http2] utilize the pull interface
handle unexpected EOF as abrupt close
[http2] fix deadlock w. client (need to send all possible data before waiting for window-update from client)
add abstraction layer to the pull interface for doing various adjustments
improve memory footprint and performance over TLS, by introducing pull mode and by gathering output into one flat buffer that can be handled at once by SSL_write (merge branch 'kazuho/expr/pulling-generator', #39 #42)