On Thu, 10 Nov 2005, Cory Nelson wrote:

>> I think I have an idea slowly growing in my head on an approach. I'll post
>> that in a separate mail in a short while.
>
> I think this will be tricky to do. I look forward to your ideas!

I've been thinking quite a bit on this and I started to write down my ideas
only to once again throw them away and go back to thinking.

I'm now leaning towards this "solution":

I'll implement the hiper API as suggested on the hiper section of the web
site. It is "simply" for high performance transfers in a single thread.

If you want to make it take advantage of SMP or doing threads for any other
reasons, I'll leave that to the application to decide and to dispatch
transfers to the proper thread.

To make a proper API that makes use of threads in a way that you suggested, I
think that is gonna be made _on top_ of the hiper suggestion as a kind of
layer that can help the app to dispatch easy-handles to the most appropriate
multi-handle-thread and then call the callback when that job is done, without
the main thread having to care about which multi-handle-thread that actually
did the job.

The fine twist with this approach is that it is rather independent of the
hiper API. And it can be done in app-space until we (if ever) implement it in
libcurl.

-- 
  Commercial curl and libcurl Technical Support: http://haxx.se/curl.html