You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
startup a server without relying on a fixed port number that may already be taken.
say you have something that spins up a listener on localhost
and forks/execs a child helper
you can pass the port
say you run a game client that does p2p, and have an out-of-band mechanism that does matchmaking
it doesn't matter which port you pick becaue you handle doing uPNP or whatever, and send the ip/port combination to the matchmaking server
etc etc etc
you can hardcode the port, but everyone picks like... 8888, 8080, 6969, 42069 etc
so having the kernel just assign one is more robust
Describe the solution you'd like
add an proc to core:net to be able to do this or something to listen_tcp
The text was updated successfully, but these errors were encountered:
As discussed on discord
I think this can be done doing something like this to get the port number
but an easier none os specific way would be nice
Is your feature request related to a problem? Please describe.
startup a server without relying on a fixed port number that may already be taken.
say you have something that spins up a listener on localhost
and forks/execs a child helper
you can pass the port
say you run a game client that does p2p, and have an out-of-band mechanism that does matchmaking
it doesn't matter which port you pick becaue you handle doing uPNP or whatever, and send the ip/port combination to the matchmaking server
etc etc etc
you can hardcode the port, but everyone picks like... 8888, 8080, 6969, 42069 etc
so having the kernel just assign one is more robust
Describe the solution you'd like
add an proc to core:net to be able to do this or something to listen_tcp
The text was updated successfully, but these errors were encountered: