Georgios Andrianakis
Georgios Andrianakis
> for now I'm really interested by the client and server use case, i.e how / when does the user start and end capture. The way things are now, the...
It does not stop. If we want to control that, we need to have our own OutputStream that can receive such "commands".
> I think that we should have an API to control start/stop recording How do you envision this would work? How would the user enable this?
How is this for an alternative: We introduce an SPI in Vert.x that allows for customizing the Netty Handler chain. That way in Quarkus we can introduce the the PcapHandler...
Ah, I wasn't aware of `NetSocketInternal#channelHandlerContext`. That is super useful, so yeah, it would be great to have it for the HTTP API as well in order to cater for...
> also I'm not convinced anymore by the interest of the feature because dump is achieved in the application layer instead of the network layer and it is not an...
> @geoand you can read this guide https://github.com/vert-x3/advanced-vertx-guide Thanks for the info! If possible, In Quarkus, I'd like to avoid having to go down to that low-level just to be...
> The users haven't changed anything in their implementation so it seems pretty evident that this has changed between Classic and Reactive. This is correct - we explicitly mention that...
Your issue is that you would like things that have a filename to not be considered a file? If so, I'm pretty sure we've discussed it before (I need to...