Ensure that the server listen on tcpip.unix
dinosaure opened this issue · 0 comments
dinosaure commented
Currently, the implementation starts an Lwt.async
process which does not Lwt_unix.listen
. So, in some complex process, even if we did the listen : stack -> unit
, it does not ensure that after we really listen on a port (and LWT did the choice to schedule such operation after something else).
By this way, such design can lead some errors such as ECONNREFUSED
because we want to start a client and LWT did not yet apply Lwt_unix.listen
.