I am confused >>You can use the SO_RCVTIMEO socket option to set the recv() operation's timeout it means I could set receive timeout for receive timeout, but I could not use it for connect timeout. Am I right? So write is is not time out, Listen is no timeout
In normal requirement, the receive timeout are already meet 80% requirement. On Wed, Dec 3, 2008 at 5:40 PM, ajeet_kr <[EMAIL PROTECTED]>wrote: > > Dear All, > Thank you Kieran. Only select() function is supporting time out, no other > function support timeout. > Regards, > Ajeet > > > Kieran Mansley wrote: > > > > On Tue, 2008-12-02 at 22:25 -0800, ajeet_kr wrote: > >> Dear all, > >> I want to know it is possible to set timeout in blocking mode socket. > >> Please > >> suggest me on this.How we can do. > > > > I don't think lwIP supports this in general. Most socket operations are > > blocking, some support non-blocking, and a few like select() support a > > timeout. You can use the SO_RCVTIMEO socket option to set the recv() > > operation's timeout. > > > > Kieran > > > > > > > > _______________________________________________ > > lwip-users mailing list > > [email protected] > > http://lists.nongnu.org/mailman/listinfo/lwip-users > > > > > > -- > View this message in context: > http://www.nabble.com/How-we-can-set-timeout-in-blocking-socket-tp20807501p20809684.html > Sent from the lwip-users mailing list archive at Nabble.com. > > > > _______________________________________________ > lwip-users mailing list > [email protected] > http://lists.nongnu.org/mailman/listinfo/lwip-users >
_______________________________________________ lwip-users mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/lwip-users
