🚀 go-pugleaf

Remy Lebeau (TeamB) wrote:

>"Bob Gonder" <notbg@notmindspring.invalid> wrote in message
>news:2f63205sghfq244hhc2obsdnk25jn6852r@4ax.com...
>
>doesn't mean every machine on the entire network with get the packet.  More
>times then not, routers will block the broadcast packets when they arrive.
>And since UDP is a connectionless protocol, the sender of the broadcast will
>never know that the packets were blocked.

Right now, the "packets" are blocked by the user being out of earshot.
This is an attempt to subvert the user's right to leave the app
running with locked data.
Are you suggesting PGM instead of UDP?
Does there have to be a SENDER? Or can everyone be a RECEIVER?
99.9dup(1000)% of the time, the app is a receiver. The rest of the
time, it's a sender.

>way in terms of the API as a TCP Socket does, except for the socket type is
>different (SOCK_DGRAM vs. SOCK_STREAM).

Yeah, got that far... just not sure what comes after that...... bind,
listen, connect, access, recv....slogging on...

I'd like to just poll the socket while waiting for a keystroke. I
might never get anything during the life of the app. Or I might get a
request to close all files, or comit suicide.  Or my user might start
a special process, and I would want to send a close-all-files signal
to my siblings. That I think needs connect and send.

I _could_ just set a file on the server, but since each instance might
be hitting it 1000 times a sec, I figure network congestion would rule
that out.   A global semifore is what I want (or maybe an octifore).