[TBD] Plans for Volo-HTTP 0.3

[yukiiiteru]

It is expected that the remaining requirements for v0.2.x will be completed this month, ref: #355

And development of v0.3.0 will begin next month.

Big Changes

Server

• Support HTTP/2 (through hyper_util::server::conn::auto)
  • It was delayed because we really needed set_max_headers but it was not done while we were developing Volo-HTTP v0.2.0
• Support connection upgrades (for WebSocket and Tunnel and more)
  • feat(http): support websocket server #481

Client

• Refactor Client and make it more easier to use, in other words:
  • Less Result with unwrap
    • chore(volo-http): use less Result in client #509
  • More friendly interfaces (#[cfg(...)] in params of function is too ugly)
    • chore(volo-http): refactor ClientBuilder, Target and CallOpt #528
• Support connection pool
  • hyper::client doesn't support connection pooling, and hyper_util::client::legacy isn't extensible enough (e.g. we support unix domain sockets now, shared memory ipc will be supported in the future, and we also support custom service discovery. Although these can work with the legacy client, it would be too complicated and ugly to do so).
  • Thus, we must implement it in volo

Small Changes

• WebSocket (server)
  • feat(http): support websocket server #481
• Tunnel (server)
• Adjust positions of modules
  • chore(volo-http): adjust positions of some mods #499

Utilities

• Bench in GitHub CI