[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [lwip-users] flow of lwip as a stream client
From: |
Simon Goldschmidt |
Subject: |
Re: [lwip-users] flow of lwip as a stream client |
Date: |
Fri, 02 Mar 2012 10:53:35 +0100 |
trex7 <address@hidden> wrote:
> >>I think that you should buffer the pbufs, and NOT call tcp_recved()
> >> until you consume a pbuf in your audio task.
>
> Nice Idea but thats one of the purpose of the buffer, to buffer the stream
> so we can call tcp_recved as soon as possible so lwip can advertise a
> larger
> window.
That only makes sense if your private buffer is well bigger than the TCP
window. In that case, only call tcp_recved() when you know you can add
additional data to your buffer, i.e. when free_byte_in_buffer >= TCP_WINDOW.
If you use this "streaming client" only in internal networks, there might not
be a problem with the unnecessary retransmissions I keep speaking of. However,
when your device is connected to a more global network (like, say, the
internet), unnecessary retransmissions should be avoided in any case. Also note
that transmission speed is throttled on packet loss/retransmissions (as a
feature of TCP).
Simon
--
NEU: FreePhone 3-fach-Flat mit kostenlosem Smartphone!
Jetzt informieren: http://mobile.1und1.de/?ac=OM.PW.PW003K20328T7073a
- [lwip-users] flow of lwip as a stream client, trex7, 2012/03/01
- Re: [lwip-users] flow of lwip as a stream client, Robert, 2012/03/01
- Re: [lwip-users] flow of lwip as a stream client, address@hidden, 2012/03/01
- Re: [lwip-users] flow of lwip as a stream client, mat henshall, 2012/03/01
- Re: [lwip-users] flow of lwip as a stream client, address@hidden, 2012/03/01
- Re: [lwip-users] flow of lwip as a stream client, trex7, 2012/03/02
- Re: [lwip-users] flow of lwip as a stream client, Simon Goldschmidt, 2012/03/02