[feature request]Could you add a feature for split port number listener for TCP and UDP in portal URL command?

[egg1234]

Currently, your portal sample only allows us to listen to the same port number for TCP and UDP.

Could you add a feature for split port number listener for TCP and UDP in portal URL command?

For example:

the portal URL command like tcpport=2077&udpport=3088

and the vector URL command like tcpport=2077&udpport=3088

Thank you very much!

[yosebyte]

Nice. Any additional requests along with this divided-port feat?

[AdamWilliam69]

1. Implement dynamic QUIC flow-control switching, allowing it to dynamically switch between three levels based on RTT and packet loss rate, rather than fixing the level at startup.
2. Introduce a configurable Mux (multiplexing) concurrency limit for the TLS/TCP side, similar to QUIC, to prevent head-of-line blocking on a single TCP connection under high-concurrency scenarios.
3. Support a connection warm-up mechanism to reduce reconnection latency after QUIC 0-RTT fails.

[yosebyte]

@egg1234 we've gone further per your request and find out a new way to redesign the runtime url, stay tuned in dev/2.

[yosebyte]

1. Implement dynamic QUIC flow-control switching, allowing it to dynamically switch between three levels based on RTT and packet loss rate, rather than fixing the level at startup.
2. Introduce a configurable Mux (multiplexing) concurrency limit for the TLS/TCP side, similar to QUIC, to prevent head-of-line blocking on a single TCP connection under high-concurrency scenarios.
3. Support a connection warm-up mechanism to reduce reconnection latency after QUIC 0-RTT fails.

@AdamWilliam69

1. Need more info about your test results, especially which threes. Yet this will increase configuration complexity.
2. Multiplex has already been introduced in v1.8.2 with "mux=1" to enable.
3. Connection pooling has been removed since multiplex has been introduced.

[AdamWilliam69]

OK let me check the new version.