Upgrades both the client example and server example. The server example is now based on hyper's new server implementation guide.
What was hyper 0.14 has now been split up into multiple crates. Hyper 1.0 also removes Server and consequentially there are no direct alternatives for a UnixServerExt to extend, though the upgrade guide does mention
That recommendation for hyper_util::server::conn::auto::Builder isn't a replacement for the old Server type, as it handles single socket/tcp connections at a time, rather than implementing a looping listener that automatically accepts all new connections.
Testing
All the tests were preserved and updated.
I also tested this update to hyperlocal using my Docker engine client crate which connects via Unix sockets by default.
Questions
With the removal of src/server.rs, the server trait now only controls the additional dependencies required by examples/server.rs - which a client obviously wouldn't want. Should we keep the feature configuration of this crate as it is, or do you have some thoughts on changing the features? Should we rename the server feature to server-example ?
Do you want the crate version updated in this PR, or left alone? If updated, do you want 0.9.0 or 0.9.0-alpha in this PR or something else?
Upgrades
hyper
from 0.14 to 1.1.Their upgrade guide
Upgrades both the client example and server example. The server example is now based on hyper's new server implementation guide.
What was hyper 0.14 has now been split up into multiple crates. Hyper 1.0 also removes
Server
and consequentially there are no direct alternatives for aUnixServerExt
to extend, though the upgrade guide does mentionThat recommendation for
hyper_util::server::conn::auto::Builder
isn't a replacement for the oldServer
type, as it handles single socket/tcp connections at a time, rather than implementing a looping listener that automatically accepts all new connections.Testing
hyperlocal
using my Docker engine client crate which connects via Unix sockets by default.Questions
With the removal of
src/server.rs
, theserver
trait now only controls the additional dependencies required byexamples/server.rs
- which a client obviously wouldn't want. Should we keep the feature configuration of this crate as it is, or do you have some thoughts on changing the features? Should we rename theserver
feature toserver-example
?Do you want the crate version updated in this PR, or left alone? If updated, do you want
0.9.0
or0.9.0-alpha
in this PR or something else?