Re: FTPAPI & timeout

[Scott Klement <sk@xxxxxxxxxxxxxxxx>]

Sender: Scott Klement <sk@xxxxxxxxxxxxxxxx>

> IMHO blocking sockets only make sense in a threaded environment where it 
> does not matter if a child thread hangs forever as long as the main 
> thread remains responsive.

...or in a situation where you use something else, like signals, to make 
sure you don't get hung up.

> I propose the change of FTPAPI to always use non-blocking sockets, regardless 
> if there has been a timeout requested or not, with using a default timeout 
> (suggestions?) in case none was provided.

That sounds good to me.  In fact, that's something I was planning to do 
with FTPAPI in the future -- I've just had too many other things to do. 
Non-blocking is the best choice, and when I wrote HTTPAPI I made sure 
everything in that one was non-blocking.
-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubsribe from the list send mail
to majordomo@xxxxxxxxxxxxx with the body: unsubscribe ftpapi mymailaddr
-----------------------------------------------------------------------