UDP broadcast/receive notification system

  • Thread starter Thread starter Mark
  • Start date Start date
M

Mark

Hi...

Didn't see another group that would be more specific for this.

I inherited from another programmer a C# class using the System.Net.Sockets
classes to implement a udp broadcast/receive notification system so that all
the machines on a subnet can keep up-to-date on events.

In his classes, he prefaces each broadcast message with a guid so that when
a message comes in he can check to see if it's one he just sent. This
spurred a couple of questions for me:
1) I haven't yet seen a message I drop on the broadcast address come back on
my receiver socket. Was this just speculative overkill on his part?

2) Now I know this sounds a little daft, but he purposely set it up so that
multiple processes on the same box can both broadcast and receive. Would I
see the message coming from my box on one of the other processes (if I get
one started up) that's listening on the same port? Did I not get my message
back because the socket classes recognize my identity down the the process
level?

Thanks
Mark
 
Thanks for the reply, Pete...
[...]
In his classes, he prefaces each broadcast message with a guid so that
when
a message comes in he can check to see if it's one he just sent. This
spurred a couple of questions for me:
1) I haven't yet seen a message I drop on the broadcast address come
back on my receiver socket. Was this just speculative overkill on his part?
Click to expand...

Are you sure that's all he's using it for? He may be also (or instead)
using the GUID to detect duplicated datagrams at the recipient end.

My recollection is that the sending socket won't get echos, so if that's
all he's doing, yes...that's probably overkill. But it's possible that's
not all he's doing.
Click to expand...

Well, that's what the comment next to the code says he was trying to do. In
any case, when I run the program and cause a message to be sent, I don't see
the message come by the receiving socket in the same process.

There's one socket opened that uses IPAddress.Broadcast to do the sending,
then there's another socket opened on my ip and bound to the same port for
receiving. As you mentioned, the receiving socket has
SocketOptionName.ReuseAddress set so that other processes can open it too.

I haven't tried running up multiple processes using the same object to see
if one of the other guys would get it but the sender currently isn't...

Thanks
Mark
 
Hi...

Didn't see another group that would be more specific for this.

I inherited from another programmer a C# class using the System.Net.Sockets
classes to implement a udp broadcast/receive notification system so that all
the machines on a subnet can keep up-to-date on events.

In his classes, he prefaces each broadcast message with a guid so that when
a message comes in he can check to see if it's one he just sent. This
spurred a couple of questions for me:
1) I haven't yet seen a message I drop on the broadcast address come back on
my receiver socket. Was this just speculative overkill on his part?
Click to expand...

Unless the Sockets documentation specifically addresses this behavior,
I think it would be prudent to have code to notice this. It is
possible that this behavior is not a result of .NET code, but of code
in the OS or LAN card driver, either of which might change in the
future.
 
Back
Top