update docs. preparing 0.7.0-alpha.0.

CHANGELOG.md

@@ -4,7 +4,7 @@
 
 - Breaking: `hyper`-1.0 for both server and client modules.
 - Breaking: Remove `override_host` option in upstream options. Add a reverse option, i.e., `disable_override_host`. That is, `rpxy` always override the host header by the upstream hostname by default.
-- Breaking: Introduced `hyper-tls-backend` feature to use the native TLS engine to access backend applications.
+- Breaking: Introduced `native-tls-backend` feature to use the native TLS engine to access backend applications.
 - Redesigned: Cache structure is totally redesigned with more memory-efficient way to read from cache file, and more secure way to strongly bind memory-objects with files with hash values.
 - Redesigned: HTTP body handling flow is also redesigned with more memory-and-time efficient techniques without putting the whole objects on memory by using `futures::stream::Stream` and `futures::channel::mpsc`
 - Refactor: lots of minor improvements

TODO.md

@@ -1,5 +1,6 @@
 # TODO List
 
+- Support of `rustls-0.22` along with `hyper-1.0`. Maybe `hyper-rustls` is the most difficult part.
 - [Done in 0.6.0] But we need more sophistication on `Forwarder` struct. ~~Fix strategy for `h2c` requests on forwarded requests upstream. This needs to update forwarder definition. Also, maybe forwarder would have a cache corresponding to the following task.~~
 - [Initial implementation in v0.6.0] ~~**Cache option for the response with `Cache-Control: public` header directive ([#55](https://github.com/junkurihara/rust-rpxy/issues/55))**~~ Using `lru` crate might be inefficient in terms of the speed.
   - Consider more sophisticated architecture for cache