Is your feature request related to a problem? Please describe.
No
Describe the solution you'd like
A step during the initial handshake of the TCP protocol where (alongside authenticating the user), the client sends a payload with some form of identifier of the target server (See, HTTP/S server header). This could theoretically allow for multiple (higher performance) servers to be hosted through a proxy of some sort, allowing for proxying through a specialized application (and to a degree, removing the necessity of UPnP support (#273)
Describe alternatives you've considered
My previous suggestion of UPnP support (#273)
Additional context
I was experimenting with a custom proxy before working on the suggestion in #273 and noticed a lack of this in the protocol from my brief digging. It would allow advanced users to assign individual subdomains to a server for example play.myserver.tld, and have multiple servers running off of a single public port. That is the only real use case I see for this.
Is your feature request related to a problem? Please describe. No
Describe the solution you'd like A step during the initial handshake of the TCP protocol where (alongside authenticating the user), the client sends a payload with some form of identifier of the target server (See, HTTP/S server header). This could theoretically allow for multiple (higher performance) servers to be hosted through a proxy of some sort, allowing for proxying through a specialized application (and to a degree, removing the necessity of UPnP support (#273)
Describe alternatives you've considered My previous suggestion of UPnP support (#273)
Additional context I was experimenting with a custom proxy before working on the suggestion in #273 and noticed a lack of this in the protocol from my brief digging. It would allow advanced users to assign individual subdomains to a server for example
play.myserver.tld, and have multiple servers running off of a single public port. That is the only real use case I see for this.