Allow access to underlying Mint connection

[bcardarella]

I'm looking into enabling web sockets for Req, however with Req relying on Finch currently Finch doesn't provide the underlying Mint connection back. If it did then Req could possibly wrap mint_web_socket

While it could be an API change I think this would have value to any library that is wrapping Finch

[sneako]

Hi @bcardarella !

The idea of enabling WebSockets in Req is certainly interesting, but this sounds like quite a major change to Finch so I have to admit its not an idea that very excited about.

I haven't put too much thought in to the idea, but is there any possibility that mint_web_socket could be implemented as a third pool type (http1, http2, websocket)? Or do you think the semantics of websockets are just too different for that to be feasible?

[recursiveGecko]

Hi @sneako

I'd also like Finch to expose the Mint connection but for a different reason. I'm using Req with long-running streaming responses (into: &req_handler/2) and I'd like to monitor the underlying TCP socket using the :inet and :socket modules

https://www.erlang.org/doc/apps/kernel/inet.html#getstat/2

https://www.erlang.org/doc/apps/kernel/socket.html#ioctl/2