On Wed, 26 Feb 2014, stuxxn wrote:

> I get an event. My socket function (CURLMOPT_SOCKETFUNCTION) gets called
> with the action parameter "1" and then i call "boost::socket.:async_write"
> to wait for write readiness.

...

> Then I have no reaason to call the socket_action again because i have no
> timeout set and my "boost::socket.:async_write" does not complete.

That seems like a correct assumption.

> This is why I asked if it could be "asio" fault because it wont trigger an
> error if the socket it is using in the async_write call is not connected.

It shouldn't "trigger an error".

The socket will become writable when connect() is completed and then your
application should notice this and you should call libcurl accordingly. If
your event library hides that information from you, then you have a problem to
solve. It seems plausible this shortcoming causes the problem you see.

-- 
  / daniel.haxx.se
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette:  http://curl.haxx.se/mail/etiquette.html