Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Thoughts and notes #2

Open
danneu opened this issue Mar 20, 2018 · 0 comments
Open

Thoughts and notes #2

danneu opened this issue Mar 20, 2018 · 0 comments

Comments

@danneu
Copy link
Owner

danneu commented Mar 20, 2018

  • The upcoming Hyper 0.12.x will make improvements to Body like allow Body construction from a Stream.
  • Hyper is also migrating to https://github.com/hyperium/http which will incur substantial API changes.
  • I'm not sure which is the best way to start a Hyper server. There are a variety of options because so many different objects can collaborate across various packages. I'm not sure if I'm supposed to use tokio, tokio-core, tokio-io, nor what the intended mix is. I'm also not sure of the performance differences between things like tokio's Runtime, the reactor Core, and other executors.
  • I rewrote this project in an effort to split my originally monolithic Service into middleware. However, during the process, I've become uncertain of the execution model. For example, I would have thought that hunk would perform a lot worse than it does, and I'm not sure where its issues lie. I seem to pass hunk's threadpool around out of superstition than deliberate strategy.

Useful:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant