On Sun, 5 Aug 2012, André Cruz wrote:

> 1- From what I read, libcurl is event-based

libcurl supports event-based handling, yes. It can also be used for
"traditional" socket use.

> I've noticed that the thread that calls my READFUNCTION callback is not the
> same thread that I used to call curl.perform().

That's incorrect. libcurl will not start new threads.

> Is this libcurl's event-loop thread?

There is no such thing.

> This means that I cannot call blocking functions in that callback, right?

When you call blocking functions in the callback, you block the transfer until
your callback returns.

> Does libcurl use only one thread for all its operations?

It uses the same thread that calls it.

-- 
  / daniel.haxx.se

_______________________________________________
http://cool.haxx.se/cgi-bin/mailman/listinfo/curl-and-python
Received on 2012-08-05