On Thu, 7 Jun 2001, Marcio Marchini wrote:
> I was just wondering if it would make more sense for ht://Dig to use
> libcurl (http://curl.haxx.se/libcurl/) in order to support many
> different protocols (https, etc)
Yes and no. In the 3.1 code, things are pretty much tied to HTTP. In the
3.2 code, things have opened up and there are already several different
protocols implemented (HTTP, HTTPS, file://, NNTP). We didn't tie in a
separate library because this would introduce an additional
dependency. (Beyond libz, the Berkeley DB, and the compilers).
Of course the 3.2 code also introduces the idea of an external transport
script, so you can handle any protocol you want by writing a small script
to retrieve the URL.
--
-Geoff Hutchison
Williams Students Online
http://wso.williams.edu/
_______________________________________________
htdig-general mailing list <[EMAIL PROTECTED]>
To unsubscribe, send a message to <[EMAIL PROTECTED]> with a
subject of unsubscribe
FAQ: http://htdig.sourceforge.net/FAQ.html
