On 11/25/2018 4:11 AM, Bogdan Popa wrote:
One way you might also solve this on UNIX systems is you could fork
after listening on the socket. The file descriptor for the socket from
the parent would then be shared with the children and so their accept
calls would be "load balanced" by way of them all accepting
connections from the same queue. This solves the problem without
requiring SO_REUSEPORT (the disadvantage being that there's only a
single kernel-level accept queue with this approach, whereas with
SO_REUSEPORT each process would get its own queue).
Is there a way to fork(2) in Racket?
Unfortunately, no. Racket is cross-platform, and Windows doesn't have
the concept of fork().
George
--
You received this message because you are subscribed to the Google Groups "Racket
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
