4 Aug
2011
4 Aug
'11
9:42 p.m.
Henning Westerholt writes:
this is the result of the different server design for
UDP and TCP. For
TCP
AFAIK one main dispatcher accepts all the connections and then
distribute them
to the workers. For UDP the workers listen directly on the (one) network
socket, so there is no dispatcher. It looks like a waste of resources,
but its from a implementation POV much easier.
in that case, it would make sense to be able to define per udp listen
address, how many processes are spawned, since seldom all addresses are
equally busy.
-- juha