[En-Nut-Discussion] Problem with UDP sockets

[Ralph Mason]

Sounds like a problem with your protocol is more to blame.

UDP has no guaranteed delivery so you need to make your protocol aware of
that and handle it accordingly. You are correct there is no flow control
other than network contention.

This is why tcp was invented.

Ralph


> -----Original Message-----
> From: en-nut-discussion-admin at egnite.de
> [mailto:en-nut-discussion-admin at egnite.de]On Behalf Of Martin Kresse
> Sent: Tuesday, 14 October 2003 8:09
> To: en-nut-discussion at egnite.de
> Subject: Re: [En-Nut-Discussion] Problem with UDP sockets
>
>
> Hi,
>
> I think I have the same problem. I want my ethernut (the client) to
> periodically request a certain amount of data from the server, which
> will then send a couple of packets containing the data back to the
> ethernut. I found out that the server must not not send the packets out
> too fast, or otherwise the nut isn't able to keep up, and calls to
> NutUdpReceiveFrom() return with 0. The "Timeout-errors" disappeared
> after I added some delays in  the server (which renders my protocol
> useless). I believe this is due to the fact, that UDP is not only
> connectionless but also lacks any automated flow control, and Nut/Net
> (please correct me if this is wrong) buffers only a single incoming UDP
> packet.
>
> Martin
>
>
> _______________________________________________
> En-Nut-Discussion mailing list
> En-Nut-Discussion at egnite.de
> http://www.egnite.de/mailman/listinfo/en-nut-discussion
>
> ---
> Incoming mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.516 / Virus Database: 313 - Release Date: 1/09/2003
>