lwip-users
[Top][All Lists]
Advanced

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

Re: [lwip-users] flow of lwip as a stream client


From: Bill Auerbach
Subject: Re: [lwip-users] flow of lwip as a stream client
Date: Fri, 2 Mar 2012 09:49:31 -0500

It seems from reading this discussion that perhaps tcp_recved is badly
named.  It's not that it's been received but that it's been processed.  I
would think tcp_processed (or similar) would convey a better meaning as to
what this function is accomplishing.

>-----Original Message-----
>Calling tcp_recved() gives the server permission to send more data, so
>you can use this to throttle the server. The server will never send more
>data than fits into the TCP window, so if you implement this correctly,
>you will *never* get more data than you can buffer. The only requirement
>here is that sizeof(your_buffer) >= TCP_WND.





reply via email to

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