mmmray

I'll take over this PR. I might add some more things if there is time. I hope to have it ready by sunday. @APT-ZERO The answer is, yes can be...

I think this satisfies all requirements from https://github.com/XTLS/Xray-core/issues/3560#issuecomment-2247495778 The mux manager now works at `http.RoundTripper` level, and muxes individual HTTP requests instead of virtual connections. I think this is better...

Right now this don't apply to http/1.1 at all. http/1.1 doesn't have mux, but actually it has request pipelining, so maybe these settings should still be applied to that functionality...

@RPRX about this PR, do you have opinions on: * behavior of http/1.1 (`httpMux` could control pipelining) * defaults (for example, we could default to `{"connections": 8}`) otherwise I'll just...

This idea was discussed privately with OP for a while. To clarify, the added noise packets work for some protocols and disrupt others, but for QUIC/H3 it allegedly works with...

the config parsing for fragment is really extreme levels of copy-pasting, and it seems that in order to be consistent with it, `delay` should be uint. maybe it should be...

it is very unlikely to work for any TCP-based protocol. let's try to focus on getting this PR merged and discuss other ideas elsewhere...

Thanks, fair enough. I think this commit should fix it, please check it... although this noise generator is mostly for a freedom dialerProxy on the tunnel's connection, and so I...

> Implementing high-availability just so I understand this correctly, the header value is tacked onto any existing transport connection, but the intent is not to do any sort of connection...

hello @amir-devman please review if this API is sufficient for your usecase as well. the implementation looks fine to me at a glance, as it is disabled by default performance...