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
A listen (_tcp / _udp) function exists, but there's no way to not listen to that port anymore. Now, in some use cases (e.g. a DNS resolver), all that is needed is "send packet from port P to Y:P'" and "wait for an answer to port P (from Y:P')", but once the answer is received, the listening socket on port P can be safely closed.
Also note that the current semantics of calliing listen mutliple times with the same port on the same stack diverges between socket and direct stack -- the socket stack will fail (ADDRINUSE), the direct stack will overwrite the listener.
The text was updated successfully, but these errors were encountered:
CHANGES:
* Adapt to mirage-protocols 6.0.0 API (mirage/mirage-tcpip#457@hannesm)
* TCP and UDP now have a listen and unlisten function (fixesmirage/mirage-tcpip#452)
* type ipinput (in TCP and UDP) and listener (in TCP) have been removed
A
listen
(_tcp
/_udp
) function exists, but there's no way to not listen to that port anymore. Now, in some use cases (e.g. a DNS resolver), all that is needed is "send packet from port P to Y:P'" and "wait for an answer to port P (from Y:P')", but once the answer is received, the listening socket on port P can be safely closed.Also note that the current semantics of calliing
listen
mutliple times with the same port on the same stack diverges between socket and direct stack -- the socket stack will fail (ADDRINUSE), the direct stack will overwrite the listener.The text was updated successfully, but these errors were encountered: