[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [lwip-users] Suggestion2

From: Mike Kleshov
Subject: Re: [lwip-users] Suggestion2
Date: Fri, 31 Jul 2009 10:07:21 +0400

2009/7/31 Oscar F <address@hidden>:
> thank you, and another question, ¿with this API, can i receive and send the
> command? TCP or UDP? and what is your advice about to have one socket open
> permanent or one socket  for every commmunication?

The answer to the question 'TCP or UDP' will depend on the
requirements of your application. You know them better than anyone on
this list.
An you know, UDP is basically exchange of datagrams. Those are limited
in size and you have to be prepared that occasionally they will not
reach their destination. TCP allows you to stream data (no limit on
data size) and it gives you reliable transport (retransmissions are
handled automatically) but that comes at a cost: TCP code is much more
complex and you have almost no control of the retransmission algorithm
which can be too slow for some applications.

- mike

reply via email to

[Prev in Thread] Current Thread [Next in Thread]