3 Commits

Author	SHA1	Message	Date
HoneyryderChuck	48961d6c64	do not select on an http/2 connection with no ongoing comms ... It was observed that, during a request done via a DoH resolve, the resolver connection is left in the selector, despite already having resolved the name, until the whole transfer is done. This is inefficient, as we're not expected to use it again. Fixed by improvinng the interest calculation of an HTTP/2 connection; if the connection doesn't have anything to write. and there aren't any inflight streams nor pings, connection won't be listened on.	2021-02-21 16:09:45 +00:00
HoneyryderChuck	267f320fe0	updated signatures to use latest interface additions in rbs	2020-11-04 01:21:28 +00:00
HoneyryderChuck	936a8533a7	initial signatures for typed ruby	2020-10-27 17:00:44 +00:00