[Prev][Next][Index][Thread]
Re: WWWLib 3.1 & blocking I/O
-
To: www-lib@w3.org
-
Subject: Re: WWWLib 3.1 & blocking I/O
-
From: mitch@tam.net (Mitch DeShields)
-
Date: Fri, 22 Sep 1995 11:12:09 -0700
-
From mitch@tam.net Fri Sep 22 14: 11:54 1995
-
Message-Id: <19950922181203953.AAA240@MITCH.tam.net>
-
X-Mailer: Windows Eudora Pro Version 2.1.2
-
X-Sender: mitch@mail.tam.net
At 05:03 pm 9/20/95 -0700, you wrote:
>Mitch DeShields writes:
> >
> > I'm using the WWWLib 3.1 in a Windows environment. I'd like to use the
> > asynchronous winsock. ...
> >
> > I find that the call to connect() in HTDoConnect() returns WSAWOULDBLOCK.
> >
> > Does my message handler need to do anything (like call LoadHTTP() again to
> > get back into the state machine)?
>
>Assuming that WWWLib 3.1 work the same way as 3.0, you just need to
>re-call whatever lib call you originally made (i.e. LoadHTTP) that
>returned WSAWOULDBLOCK.
Yep, this seems to be mostly working. My message handler gets called with
FD_CONNECT, then one or more FD_READ notifications. In each case, I call
HTTPLoad(). This part is working, I can see the received bytes in the read
buffer.
However, I never get an FD_CLOSE notification. I would think that (on a
GET) the HTTP server would close the socket after sending the information to
the client. The FD_CLOSE flag is included in the lEvent in
WSAAsyncSelect(), and I do get other notifications. I have even tried to
close the socket (closesocket()) from a button press event.
Why no FD_CLOSE notification????
Thanks in advance.
____ ____ ____ ____ ____ ____ ____ ____ ____ ____
/ __\/ __\/ __\/ __\/ __\/ __\/ __\/ __\/ __\/ __|
| /__/ /__/ /__/ /__/ /__/ /__/ /__/ /__/ /__/ /__|
|_/ \___/ \___/ \___/ \___/ \___/ \___/ \___/ \___/ \___/ \_|
Mitch DeShields IQ Interface 207 Second St. Suite B
mitch@tam.net (415) 331-0304 Sausalito CA 94965