Andrei Pangin
Andrei Pangin
FYI, [async-profiler](https://github.com/jvm-profiling-tools/async-profiler) has a [converter](https://github.com/jvm-profiling-tools/async-profiler/blob/v2.0/src/converter/jfr2flame.java) from JFR to FlameGraph, compatible with JDK 11 recordings. ``` java -cp converter.jar jfr2flame input.jfr output.html ``` converter.jar is included in [all new releases](https://github.com/jvm-profiling-tools/async-profiler/releases).
Fixed in one-nio 1.6.0
Yes, there are long-term plans for that, but it's unlikely that a production-ready solution will appear here in the nearest months.
I'd say, RPC is NOT a good example for QUIC (if we talk about RPC in the context of communication between microservices). QUIC is mostly beneficial for end user experience,...
To extend my previous message: nearly all benefits of QUIC are useless in the RPC scenario: - Zero RTT: not important, since a connection to another service is typically opened...
300 ms RTT is the opposite side of the globe. I just don't have experience of doing RPC in such configuration.
I think `HttpServer.handleRequest` is a right extension point for this. What alternatives can you suggest if it does not suit?
Well, this is not really a request filter. It's more like partial or wildcard path matching that I'm going to implement some time soon.
Thanks. I'm working on the English documentation for the library.
Sorry, no resources for the documentation, unfortunately. I'd be glad to accept contributions.