From: ygrek <ygrekheretix@gmail.com>
To: caml-list@inria.fr
Subject: [Caml-list] [ANN] ocurl forked and 0.5.4 released
Date: Thu, 31 Jan 2013 01:03:39 +0200 [thread overview]
Message-ID: <20130131010339.0bb90e1aca528ff49339998f@gmail.com> (raw)
Hello,
Let me announce the existence of the new ocurl project, namely at http://ocurl.forge.ocamlcore.org/
This project is the fork of http://ocurl.sourceforge.net/ and accumulates many bugfixes and
enhancements which didn't make it to the original version, including the multi API wrappers
and pluggable asynchronous interface (which makes it possible to inject curl transfers in
your event loop of choice). This is the first release for the fork, that incorporates all
the bugfixes and new features from 3 years of its history, except the asynchronous api.
Next release will merge branch event.
I would like to thank Lars Nilsson, the original author of ocurl, who brought this project to existence.
Hope the forked version will prove useful.
--
ygrek
http://ygrek.org.ua
next reply other threads:[~2013-01-30 23:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-30 23:03 ygrek [this message]
2013-01-31 9:21 ` Goswin von Brederlow
2013-02-02 10:27 ` Vincent B.
2013-02-04 11:06 ` Goswin von Brederlow
2013-02-05 22:33 ` ygrek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130131010339.0bb90e1aca528ff49339998f@gmail.com \
--to=ygrekheretix@gmail.com \
--cc=caml-list@inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).