- From: Andrew Wong <wong@powertv.com>
- Date: Fri, 19 Mar 1999 09:53:20 -0800
- To: Henrik Frystyk Nielsen <frystyk@w3.org>, www-lib@w3.org
>>GDB trace showed that the failure caused at the very first call to connect() >>i.e. before HTLoadAnchor() returns. And therefore HTEventList_loop() in >>showlinks.c doesn't even get chance to run. > >I don't think it fails but rather it doesn't complete because you are using >non-blocking sockets. Non-blocking sockets (non-preemptive mode) require an >eventloop that libwww can use (this doesn't have to be the default libwww >eventloop: No, it's not because of non-blocking. If it doesn't complete, it will set EINPROGRESS to errno rather than ENOENT (which leads to a TCP_ERROR) Andrew
Received on Friday, 19 March 1999 12:53:25 UTC