Yes

Since we've had to switch over to use non-blocking sockets all over, we need
to add proper code to deal with this nicely. I won't release any public
version until we have this fixed (and tested in a pre-release or two).

Everywhere where curl writes to or reads from sockets, we need to make sure
that we not only survive EWOULDBLOCK (and equivalent codes from the SSL
layer) but also that we deal with it nicely. That would be to go back to
select() and similar until we get clearance to continue again.

I'm hoping to have this addressed during this week or in the beginning of
next week. Anyone who thinks this sounds like a fun hack, feel free to join
in! :-)

-- 
    Daniel Stenberg -- curl groks URLs -- http://curl.haxx.se/