RE: [lwip-users] sys_arch.c timeout of zero problem

2009-08-12 Thread David Shmelzer
half Of goldsi...@gmx.de Sent: Tuesday, August 11, 2009 1:30 PM To: Mailing list for lwIP users Subject: Re: [lwip-users] sys_arch.c timeout of zero problem lwIP should not have any problems with a timeout of zero. However, converting timeout valus inside the function sys_arch_mbox_fetch() (l

Re: [lwip-users] sys_arch.c timeout of zero problem

2009-08-11 Thread goldsi...@gmx.de
lwIP should not have any problems with a timeout of zero. However, converting timeout valus inside the function sys_arch_mbox_fetch() (like you did) is not supported and will confuse the stack. This is because of the way the stack handles timers: it keeps the time until the next timer expires (

[lwip-users] sys_arch.c timeout of zero problem

2009-08-11 Thread David Shmelzer
My application requires that netconn_recv() be non-blocking and to return immediately of there is no message waiting. So I modified sys_arch.c to convert small timeout values to zero for the queue wait. But I run into problems if the xQueueReceive timeout is 0. The TCP connection closes after ~5 n