RE: Downloading web pages using threads

I think that it only closes the connection when the keepalive time has
expired or when it gets disconnected from the http server.

Clint B. Suson           408-986-8988 X-255
Network Software Engr.
GWCom Inc.

> -----Original Message-----
> From: www-lib-request@w3.org [mailto:www-lib-request@w3.org]On Behalf Of
> Sam Couter
> Sent: Wednesday, April 05, 2000 11:18 PM
> To: Kaming Young
> Cc: www-lib@w3.org
> Subject: Re: Downloading web pages using threads
>
>
> Kaming Young <kmyoung7@ie.cuhk.edu.hk> wrote:
> > hi
> >
> > libwww says it do pipelining, but how does it accomplish this?
> >
> > I try to look at the trace from the Example program mget, which
> uses non-blocking and fire off pipeline requests
> >
> > but it seems that libwww put all the requests in the pending queue,
> > while waiting for response
> > and pop up a request from pending queue to pipe and send to
> server after receiving request of previous response
> >
> > i have extracted some part from the trace about socket read
> write, pls correct me if i interpret the trace incorrectly
>
> Basically, it queues requests if the pipe is busy already. When
> the request
> in the pipe is done, it pops the next one off the pending queue and starts
> it using the same connection (socket).
>
> I think once the pending queue is empty it closes the connection.
> --
> Sam Couter                                              sam@topic.com.au
> Internet Engineer                               http://www.topic.com.au/
> tSA Consulting
>

Received on Thursday, 6 April 2000 14:14:06 UTC