Re: libwww and HTTP1.0

Anybody succeed to open several simultaneous connections to a host using
www-lib??? It seems that all the non-blocking connections openned to a host
are actually handled *sequentially* (I've tried all HTTP_setConnectionMode
types). i.e. blocking after all.

Is that concurrency only available for connecting to multiple hosts???

I want stress test a server application, therefore I want to open many 
connections to generate a lot load. Is this possible with www-lib or
should I look somewhere else? And how's the progress of making www-lib
thread safe?

Thanks,

Andrew

>Hello Henrik,
>
>Thank you for your continious helping.
>
>The reason for HTTP/1.0 is following. 
>
>I want to have an option to disable pipelining, and allow
>to use several simultaneous sockets per one remote host.
>
>In HTTP/1.1 mode libwww always opens no more than one connection per remote
>host and (by default) pipelines the requests. With pipelining if the first
>request in pipeline takes long time it delays others. All my requests result
>in fact to calls of CGI scripts that takes awhile to execute.
>
>Another reason that some of the Web servers doesn't support pipelining.
>In that case HTTP/1.1 (without pipelining) more slow than HTTP/1.0.
>
>Regards,
>Mikhail

Received on Friday, 26 March 1999 21:02:18 UTC