🚀 go-pugleaf

Remy Lebeau (TeamB) wrote:

>"Hans Galema" <dontusethis@dontusethis.nl> wrote in message
>news:4020d650$1@newsgroups.borland.com...
>
>> UDP would be easy to implement. It can broadcast and so
>> no application has to know about other applications. Also
>> if your application would eventuallu run on WAN you would
>> not have to change to much.

In looking, was reminded of mailslot, so took another look at some old
code I had done a couple years back, and got that working, but it only
talks to one instance per user (any instance can talk, but only the
first can listen). So I probably need to get on with UDP.

>The thing about UDP is that it doesn't pass through network routers very
>well.  You wouldn't be able to send a UDP broadcast to the entire
>network,only your particular subnet of it.

You mean the 255.255.255.0 subnet? I think that would be acceptable.

I've googled, but haven't come up yet with example code or APIs for
UDP.  Just see mention that I need a port number, and the list of
pre-assigned ports is mind numbing.

Ok, I see I need Sockets. Gotten as far as
	UDPsocket = socket(AF_INET, SOCK_DGRAM, IPPROTO_UDP);
Still reading on MSDN, but getting tired. More later.