[Linuxtuples-devel] best effort communication

[Bram S. <br...@sa...>]

Hi,

As an optimization, I've added a best-effort communication channel
(UDP based) to the tuple server.

With this, a put_be() will use UDP to put a tuple into space,
using best effort.

I'll add replace_be() later.
get() and read() make little sense UDP based, because the comm
for those ops is 2-way, and if half of the comm can be lost, it would
cause too much headache.

Currently, the put_be() either succeeds, or fails, and ofcourse
there is no feedback to the caller.

In practice, dropped datagrams are extremely rare.
Performance-wise it is a very fast operation: no handshaking
is done, just a simple one-way-comm. This should be very
useful in high latency networks.

TODO: UDP is limited by datagram size, so tuples cannot be
too large. Currently, I have no check on size yet.

Bram