VMware offers training and certification to turbo-charge your progress.Learn more
Improvements, new features, and fixes have landed in a Maven Central mirror near you under
Bismuth-SR5 Bill Of Material. This version is now used by Spring Framework 5.0.3 and the upcoming
Spring Boot 2.0.RC1! Our site projectreactor.io has been updated with the latest versions.
A quality update including more than a dozen fixes and just a couple new features: new
Signal#getContext access to the current flow
reactor-test also welcomed new features including
Context verification facilities and a
We are now working on
3.1.4.RELEASE. Have a look at our issues backlog.
In this release, we improved our
Repeat facilities timing handling.
We are also featuring our first new advanced caching helpers for
Mono . They will allow easy storage implementation choices as well as providing the expected behavior for consuming subscribers.
Below is a quick snippet using an arbitrary hash-map that demonstrates an upstream flow is only subscribed once regardless of the multiple verifications:
Map<String, List> data = new HashMap<>(); Flux<Integer> cached = CacheFlux.lookup(data, "foo", Integer.class) .onCacheMissResume(Flux.just(1, 2, 3).log()); StepVerifier.create(cached) .expectNext(1, 2, 3) .verifyComplete(); //prints 1, 2, 3 StepVerifier.create(cached) .expectNext(1, 2, 3) .verifyComplete(); //prints nothing
We are now working on
3.1.5.RELEASE, and our community is invited to submit ideas for more extensions or operators. We already have another fantastic PR in progress from Oleg Dokuka about IO extensions for Flux
A recommended update that fixes a race condition when publishing the stream body from a different thread than one of Netty's own threads. We now also support
KQueue as an alternative to
HttpClient has been updated to emit an error on premature HTTP response completion.
We are now working on the
0.7.4.RELEASE and the following
0.8.0. Keep in mind the next major version will bring important API changes and for that reason we strongly recommend to use an adapting layer instead of exposing the
reactor-netty API directly. Or simply use
Spring Framework which does exactly that on both the client and server sides.
Last month, we had a chance to speak at SpringOne Platform. You can view the slides online and watch the video replay.