"Arnaud SAHUGUET" <sahuguet@lucent.com> writes:

> > There are cases where it just makes more sense to interface to an
> > existing C library.  I think SSL falls in this category, because the
> > SSL protocol is quite complex, and the OpenSSL implementation seems
> > of good quality.  On the other hand, the subset of HTTP that you need
> > to write CGI-like applications is simple enough that implementing it
> > directly in OCaml (like OcamlNet does) is easier than trying to
> > interface to, say, libwww.
> 
> I agree that this is fine for a subset of HTTP. But what if we need
> the whole thing.  I think the problem is not so much implementing
> something in oCaml, it is implementing something that satisfies a
> given spec (e.g. SSL, HTTP, etc.)  and maintaining it. The
> maintainance is really the hard part.  >From my point of view,
> relying on a reference implementation (e.g. libwww maintained by
> W3C) is a good way to go.


libcurl is a good alternative to libwww,

http://curl.haxx.se/
http://curl.haxx.se/libcurl/

You may also be interested in the list of http libraries,

http://curl.haxx.se/docs/comparison-table.html
http://curl.haxx.se/libcurl/competitors.html


-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners