Newsgroups : Borland : borland.public.delphi.internet.winsock : 2006 May : Re: Indy UDP readevent doesn't use dual core/multi processors?

www.cryer.info
Managed Newsgroup Archive

Re: Indy UDP readevent doesn't use dual core/multi processors?

Subject:Re: Indy UDP readevent doesn't use dual core/multi processors?
Posted by:"mike" (johnson..@zonnet.nl)
Date:3 May 2006 13:05:45

>No, because there is no way to determine the source IP/Port until the data
>is actually read from the listening socket.

You couldn't have made it clearer than by explaining it like that!

> 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?

>Yes.

I tried to lookup the destination address in a tobjectlist with
a 1000 items, I was afraid this would be too slow if it was done
in the onudpread event for every single packet, but it turns
out that it only has a 5% performance penalty, which is
acceptable for my application. I can forward about 20000 UDP
packets of 138 bytes per second on a 3.4 dual core even if I
have to do a lookup in the list for every packet!

Thanks for the great support and your great product!

Replies:

none

In response to:

www.cryer.info
Managed Newsgroup Archive