Skip to content

@violetagg violetagg released this Jan 13, 2020 · 32 commits to 0.9.x since this release

❗️ This release contains a backwards compatibility issue, v0.9.4.RELEASE was released immediately after.
Prefer using the later.

Reactor Netty 0.9.3.RELEASE is part of Dysprosium-SR3 Release Train.

See also release notes from 0.8.15 for changes that were inherited from the 0.8.x maintenance release.

New features and improvements

  • Depending on Reactor Core v3.3.2.RELEASE, see release notes (dab50bd)
  • Depending on Reactor Pool v0.1.2.RELEASE, see release notes (dab50bd)
  • Add HttpClientRequest#resourceUrl and HttpClientResponse#resourceUrl. (#901)
  • Add ability to configure maxLifeTime for connection pools. (#922, #924)
  • Add an API for disposing LoopResources with a specific quiet period and timeout (#860, #946)
  • Allow client/server to proxy PING frames instead of responding to them. (#663, #927, #945)

🐞 Bug fixes

  • Apply BND convention to shadowJar as well. (#913, #915)
  • Add more information in the logs for the connection pool that will be used. (5e6d220, #917)
  • Metrics:
    • Use nanoTime for the timers. (#930)
    • Ensure URI tag used for micrometer does not contain the query. (#926, #932)
    • Cache meters per tags. (#931, #947)
  • Ensure the global ConnectionProvider is cleared on server.dispose when the server address is not any local address. (360ab0f, #953)

📖 Documentation, Tests and Build

👍 Thanks to the following contributors that also participated to this release

@sullis, @Tankika, @JacobASeverson, @mgr32

Assets 2
You can’t perform that action at this time.