RE : RE : [lwip-users] Data waiting but no recv()

[Frédéric BERNON]

I'm not sure, so, try this on one of your sockets :

 

flag = 1;

lwip_ioctl( soc, FIONBIO, &flag):

 

 

====================================
Frédéric BERNON
HYMATOM SA
Chef de projet informatique
Microsoft Certified Professional
Tél. : +33 (0)4-67-87-61-10
Fax. : +33 (0)4-67-70-85-44
Email : address@hiddenr
Web Site : http://www.hymatom.fr
====================================

P Avant d'imprimer, penser à l'environnement

 

-----Message d'origine-----
De : address@hidden [mailto:address@hidden De la part de Piero 74
Envoyé : mercredi 23 janvier 2008 14:12
À : Mailing list for lwIP users
Objet : Re: RE : [lwip-users] Data waiting but no recv()

How i can set socket as NON-BLOCKING in lwip 1.2.0?

2008/1/23, Frédéric BERNON <address@hidden>:

For non-blocking, it should be available in 1.2.0. For SO_RCVBUF and SO_RCVTIMEO, you need 1.3.0.

 

 

 

====================================
Frédéric BERNON
HYMATOM SA
Chef de projet informatique
Microsoft Certified Professional
Tél. : +33 (0)4-67-87-61-10
Fax. : +33 (0)4-67-70-85-44
Email : address@hidden r
Web Site : http://www.hymatom.fr
====================================

P Avant d'imprimer, penser à l'environnement

 

-----Message d'origine-----
De : lwip-users-bounces+frederic.bernon=address@hidden [mailto:address@hidden] De la part de Piero 74
Envoyé : mercredi 23 janvier 2008 11:49
À : Mailing list for lwIP users
Objet : Re: [lwip-users] Data waiting but no recv()

Hi

if i use lwip 1.2.0 i CANNOT have non-blocking socket and/or LWIP_SO_RCVBUF?

please... answer me... i need to know if upgrade to 1.3.0 when available on single zip file

Thanks.
Bye,
Piero

2008/1/22, Jonathan Larmour <address@hidden>:

Josh Rothstein wrote:
>
> What is the correct way to make sure that my stack does not lock up if I
> am receiving unexpected data over a connection?  Should I just poll()
> each time around the loop?  I cannot just place extra recv()s around the
> loop or else my task will block if no data is waiting.

Theoretically, you can do it in a different task, use select() to wait for
multiple sockets when you would be blocked waiting for input anyway and/or
use non-blocking sockets if you were going to be doing a busy poll anyway.

But the more efficient choice is to enable the LWIP_SO_RCVBUF option in
lwipopts.h and use setsockopt() to set it.

Jifl
--
eCosCentric Limited      http://www.eCosCentric.com/     The eCos experts
Barnwell House, Barnwell Drive, Cambridge, UK.       Tel: +44 1223 245571
Registered in England and Wales: Reg No 4422071.
------["The best things in life aren't things."]------      Opinions==mine


_______________________________________________
lwip-users mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/lwip-users

_______________________________________________
lwip-users mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/lwip-users

Frédéric BERNON.vcf
Description: Frédéric BERNON.vcf