I like this idea, but I dont know if Hyper is the best package to go with.
Hyper occupies part of the Rust ecosystem that I think suffers from package
bloat, like much of NPM. For example, currently Hyper requires 52 packages:
autocfg, bitflags, bytes, cfg-if, fnv, fuchsia-zircon, fuchsia-zircon-sys,
futures-channel, futures-core, futures-sink, futures-task, futures-util, h2,
hashbrown, http, http-body, httparse, httpdate, indexmap, iovec, itoa,
kernel32-sys, lazy_static, libc, log, memchr, mio, miow, net2, pin-project,
pin-project-internal, pin-project-lite, pin-utils, proc-macro2, quote,
redox_syscall, slab, socket2, syn, tokio, tokio-util, tower-service, tracing,
tracing-core, try-lock, unicode-xid, want, winapi, winapi-build,
winapi-i686-pc-windows-gnu, winapi-x86_64-pc-windows-gnu, ws2_32-sys
autocfg, bitflags, bytes, cfg-if, fnv, fuchsia-zircon, fuchsia-zircon-sys, futures-channel, futures-core, futures-sink, futures-task, futures-util, h2, hashbrown, http, http-body, httparse, httpdate, indexmap, iovec, itoa, kernel32-sys, lazy_static, libc, log, memchr, mio, miow, net2, pin-project, pin-project-internal, pin-project-lite, pin-utils, proc-macro2, quote, redox_syscall, slab, socket2, syn, tokio, tokio-util, tower-service, tracing, tracing-core, try-lock, unicode-xid, want, winapi, winapi-build, winapi-i686-pc-windows-gnu, winapi-x86_64-pc-windows-gnu, ws2_32-sys