On 12/19/2016 09:31 AM, S.C.T.N Gmbh wrote:
> ok, thank you.
>
> But does it really make sense in my case, as I know that I have to expect
> one byte of payload every 100ms?
each byte you receive may be in a different datagram... UDP is not serialized
and guaranteed to arrive in order... UDP datagrams may not even make it from
the
startpoint to the endpoint...
> And moreover I am testing IP connectivity with this loop, that is, a timer
> is reset at any time the datagram is received and whenever the actual
> timespan between last receive and actual time is >100ms the SW detects that
> IP connectivity to the remote host is down.
but it may not be "down"... the datagram may simply not have made it all the
way
through the pipe... that doesn't mean the connection, as such, is down... only
that the datagram didn't make it OR that it may arrive later...
if you really want a more serial like connection, TCP is much better because
you
are guaranteed that data will arrive in the proper order, built-in error
detection/correction, two way comms over the link, you know when the connection
is terminated from either end... there are other reasons, too, but these are
the
first i can think of related to what little i know of your project...
--
NOTE: No off-list assistance is given without prior approval.
*Please keep mailing list traffic on the list* unless
private contact is specifically requested and granted.
------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today.http://sdm.link/intel
_______________________________________________
synalist-public mailing list
synalist-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/synalist-public
