Re: [lwip-users] socket functionality - nonblocking?

[Rishi Khan]

I think send is non-blocking always. yes/no??

Rishi

On Nov 25, 2008, at 9:57 AM, Micael wrote:

> On Tue, November 25, 2008 14:57, Kieran Mansley wrote:
> > On Tue, 2008-11-25 at 08:24 -0500, Rishi Khan wrote:
> > > listen is blocking? Maybe you mean accept? In any case, I have code
> > > that makes accept non-blocking and I sent it in as a patch  
> > > before ...
> > > not sure if it made it's way to the CVS repository.
> >
> > Yes, sorry, I meant accept.
>
>
> This makes me feel good. ;-)
>
> So if I have collected all information correctly, non-blocking  
> status is
> something along the lines of;
>
> Nonblocking support:
> ---------------------
> select() (also have a working timeout support)
> recv()
> listen()
> accept() - using patch from Rishi
>
> Missing Nonblocking support for:
> ---------------------------------
> connect()
> send()
>
>
>
>  Micael
>
>
>
> _______________________________________________
> lwip-users mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/lwip-users