🚀 go-pugleaf

"Bob Gonder" <notbg@notmindspring.invalid> wrote in message
news:gsh520lcgru35gfubpf1q06s7fqkk7921p@4ax.com...

> This is an attempt to subvert the user's right to leave
> the app running with locked data.

Then I do not suggest UDP for that.  UDP is not reliable in general - it
does not guarantee packet delivery nor packet byte order like TCP does.

> Are you suggesting PGM instead of UDP?

I have no idea what PGM is.

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

All of the above.  Actually, the connect() and listen() can be replaced with
sendto() and recvfrom().  But in any case, most of the socket principles are
the same regardless.

> 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).

Sounds like what you really need is a single file server that all clients go
to, and the server handles and directs the requests for data, openings,
closings, etc. and notifies the rest of the clients accordingly when needed.


Gambit