[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lwip-users] Raw TCP flow control
From: |
Peter Jolasson |
Subject: |
[lwip-users] Raw TCP flow control |
Date: |
Tue, 30 Aug 2005 14:50:30 +0200 |
Hi there,
I'm using the "raw api" for TCP communication
Normally my "callback_recv" function passes along the payload data to the application and then calls pbuf_free() and tcp_recved().
But how should I handle a situation when my application cannot accept the data? (temporary stalled for a few 100 ms)
My guess is:
Store a pointer to the pbuf and in the "callback_poll" function monitor when/if my application can receive the data and then pass along the data and call pbuf_free() and tcp_recved().
Is this the correct approach/solution? Do I have to store a list of unused pbufs or can I in some way halt the "callback_recv" function while I'm only interested in the "callback_poll"?
/Peter/
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [lwip-users] Raw TCP flow control,
Peter Jolasson <=