After looking and testing with the indy 10 snapshot, I think I misunderstood bindings at first. Is a binding defined by the host address and IP (the listening server)? Regardless of the source ip/port? My test seems to indicate that different IP/port sources that connect to my udpserver still end up in the same thread (the thread has the same PID all the time).
So does the new Indy snapshot UDPServer now have support for separate threads per binding, which means listening on
different host IP addresses? Or is it now possible to have a
thread per virtual connection (with same destination port) with a source client, if the source IP and/or port are different per thread? I am getting the feeling that due to the UDP nature
it's just impossible to have threads per "connection" like the
TCPserver has.
Am I right in assuming that:
A) To use multiple cores with udpserver I need to have multiple
(one per core) host IP adresses on the server computer and bind them?
B) I need to handle the incoming packets myself in the onudpread event and check for myself what the source IP/port is
in order to react different to each source?
Thanks for all the great help!
