On Wed, 20 Jan 2010, Leon Winter wrote:

>> Wouldn't you? Well then you speak of other ways of customizations and I
>> don't think you necessary should make them happen just because you change
>> read and write but they are rather independent. For example we already have
>> the CURLOPT_OPENSOCKETFUNCTION that lets you replace the socket() call
>> basically.
>
> Good point again, we could indeed use CURLOPT_OPENSOCKETFUNCTION along with
> CURLOPT_SOCKOPTDATA to pass our e.g. ssh channel. However there is no
> "socket close function callback" atm but also i macro sclose(). Since we are
> going to replace sread()/swrite() with callbacks, we should probably to that
> with sclose() too.

Yeah, I think so too.

> Hopefully I havent missed something again ;)

I think the best way forward from this point is to actually proceed and try to
write your application and then see what kind of hooks libcurl needs to offer
for it to work, and do some first basic shots at implementing them to see that
the app lives.

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