Oscar,
Remember, you also have to handle dropped ACKs and NACKs. J Bill From: [email protected] [mailto:[email protected]] On Behalf Of Oscar F Sent: Friday, July 31, 2009 2:15 AM To: Mailing list for lwIP users Subject: Re: [lwip-users] Suggestion2 Thanks Mike!, in few days i hope to know what protocol prefer to use the customer, i think that will be SDP, because he said me that i've to send ACK or NACK for every command. Regards Oscar On Fri, Jul 31, 2009 at 8:07 AM, Mike Kleshov <[email protected]> wrote: 2009/7/31 Oscar F <[email protected]>: > 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. Regards, - mike _______________________________________________ lwip-users mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/lwip-users
_______________________________________________ lwip-users mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/lwip-users
