It's worth comparing the behavior of the netconn API. Even though the netconn API is only available with NO_SYS = 0, it is still a user of the raw API like the applications mentioned in this email thread.
lwip_netconn_do_writemore() calls tcp_write() until all segments have been put into the TCP send buffer, then calls tcp_output(). Joel On Jul 13, 2016, at 10:36 AM, Pîrvu Mihai <[email protected]> wrote: Again, it's probably not be the wrong approach, it's just what I've been told on this thread: https://lists.gnu.org/archive/html/lwip-users/2016-06/msg00055.html Since it worked for me at that moment, I just let it like that, and reading the responses here confirms that it's the correct approach if you don't want to wait for the delay. Mihai On Wed, Jul 13, 2016 at 5:59 PM, Jakub Schmidtke <[email protected]> wrote: I think you might have missed reading the documentation: tcp_write enqueue data, tcp_outout tries to send it. You always have to call both. I actually found the recommended call flow on wiki (Here: http://lwip.wikia.com/wiki/Raw/TCP ) after Mihai mentioned using tcp_output(). And yes, I haven't fully read the docs/wiki yet, since I am trying to fix existing code written by someone else - who must have missed that... However, Mihai mentions that calling tcp_output() might be the wrong approach... Is it really? Thanks! _______________________________________________ lwip-users mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/lwip-users _______________________________________________ lwip-users mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/lwip-users
_______________________________________________ lwip-users mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/lwip-users
