On Mon, Apr 14, 2008 at 11:59:49AM -0600, Bart Whiteley wrote:
> I agree that an extra option seems like the cleanest approach thus far. I
> have found examples of applications that invent new schemes, but these are
> always specific to a certain application. I also found an example of an
> application that uses a non-numeric port field to encode the path to the
> unix socket.

That sounds pretty clean, except that it's illegal according to the
generic URI syntax.

> I guess it would be kind of nice if the path to the unix socket was encoded
> in the URL for libcurl, as this would require no changes to the WBEM client
> library. However, if we can't come up with a way to do this that feels good
> to the libcurl community, I'm totally fine with extending the API of the
> WBEM client library, or inventing some application-specific way of encoding
> the path in the URL, and then doing some URL parsing in the WBEM client
> library prior to invoking libcurl.

You could probably implement this today without modifying libcurl by using
the CURLOPT_OPENSOCKETFUNCTION callback to open the socket within your
library.

>>> Dan

-- 
http://www.MoveAnnouncer.com              The web change of address service
          Let webmasters know that your web site has moved