On Fri, 28 May 2004, Steinar Bang wrote:

> > (I can only think of one major feature we lack in comparison to libwww, and
> > that's support for pipelning.)
>
> By "pipelining", do you mean HTTP/1.1 pipelining[1]? Or do you mean a
> pipeline/stream architecture like the one libwww has, allowing for
> asynchronous behaviour in a single threaded environment[2]?

I mean HTTP pipelining. That's the main feature (not easily worked-around)
I've read people mention to be missed when they've discussed moving from
libwww to libcurl.

I don't know any libwww internals so I can't say anything about its
architecture. libcurl supports "asynchronous behaviour in a single threaded
environment" with its multi interface, I don't know how it compares to
libwww's approach.

-- 
     Daniel Stenberg -- http://curl.haxx.se -- http://daniel.haxx.se
      Dedicated custom curl help for hire: http://haxx.se/curl.html