zecfoundation
/
tower
mirror of https://github.com/ZcashFoundation/tower.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
tower/tower-spawn-ready/CHANGELOG.md

17 lines
308 B
Markdown
Raw Permalink Normal View History

Bump crates and changelog dates (#397)
2019-12-19 10:44:40 -08:00
# 0.3.0 (December 19, 2019)
Update the rest of the crates and upgrade ready cache to `std::f… (#379) * Update hedge, filter, load, load-shed, and more * Update ready cache * Prepare release for ready-cache * fix merge * Update balance * Prepare balance release
2019-12-05 11:21:47 -08:00
- Update to `tower-service 0.3`
- Update to `tokio 0.2`
- Remove `Executor` usage
Bumps for 0.3.0-alpha.2 (#355) * Bump all to futures-* alpha.19 * Prepare for alpha.2 release * Make tower-service also a path dep * Use new tokio alpha
2019-09-30 15:56:26 -07:00
# 0.3.0-alpha.2 (September 30, 2019)
- Move to `futures-*-preview 0.3.0-alpha.19`
- Move to `pin-project 0.4`
spawn-ready: Add date to changelog
2019-09-11 13:33:43 -07:00
# 0.3.0-alpha.1 (September 11, 2019)
Update tower-spawn-ready to std::future (#332) This bumps tower-spawn-ready to 0.3.0-alpha.1
2019-09-10 14:06:34 -07:00
- Move to `std::future`
spawn-ready: Drives a service's readiness on an executor (#283) Some layers cannot guarantee that they will poll inner services in a timely fashion. For instance, the balancer polls its inner services to check for readiness, but it does so randomly. If its inner service must be polled several times to become ready, e.g., because it's driving the initiation of a TLS connection, then the balancer may not drive the handshake to completion. The `SpawnReady` layer ensures that its inner service is driven to readiness by spawning a background task.
2019-05-29 09:57:46 -07:00
# 0.1.0 (unreleased)