Jakub Kozlowski

I would interested in the maintainers thoughts on this issue, I had a quick look around and there are a few things that could be blocking this: * Quic runs...

Yeah, that would be a shame, since the connection management has some nice features. Your suggestion would also be probably not so nice since RealCall doesn't really let you swap...

Thanks! I think the refactoring I described could work out, I might try to hack something together. I wonder if the maintainers would be open to a contribution like that?

> We make no API compatibility promises for our internal packages. So those changes aren’t precluded. That's what I was thinking too.

Address holds the SocketFactory that is used in the lower layers, and that's in the public API.

Yeah, but Quic uses UDP, so no SocketFactories :) maybe the way to do this is indeed just let us have something that will make a decision on what set...

Ah yes, now I remember reading the RFC. Cool, the refactoring will basically need to cleanup a bunch of code that deals directly with Sockets and then we need a...

I see you went with http1.1 over quic, that's what I attempted as well server side. Is that still the case? I was hoping to use this for internal backend...

Seeing similar thing for loglines in CassandraClientPoolingContainer when trying to serialize CassandrClient

+1, this should have rather large upside