From: Mike Gran <spk121@yahoo.com>
To: Guile User <guile-user@gnu.org>
Subject: Re: What new libraries or functionality does Guile need?
Date: Fri, 18 Jul 2008 11:38:56 -0700 (PDT) [thread overview]
Message-ID: <809243.47320.qm@web37901.mail.mud.yahoo.com> (raw)
Julian-
There are a couple of ways to do HTTP client stuff already.
TTN's Guile-WWW will do http GET. It has the advantage of being very schemey.
Depending on you Guile setup, it may need modification. Last time I tried to use it some time ago, it back-ported (fore-ported?) easily enough. IIRC there was some little thing about macros that needed to be simplified to get it to work. I don't remember exactly. It doesn't (or perhaps didn't) do POST, though.
Alternately, Guile-GNOME has the Gnome-vfs interface wrapped. This does some http client stuff.
I think either of these would be enough for simple things.
But in terms of more featureful libraries that could be adapted/wrapped, I rather like libcurl. Bigloo scheme has bindings for this one. It does all the LDAP and https stuff.
But then again libcurl doesn't do webdav.
The neon client library does do webdav.
-Mike Gran
next reply other threads:[~2008-07-18 18:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-18 18:38 Mike Gran [this message]
[not found] <cmu-lmtpd-5742-1216742728-1@mail-imap1.uio.no>
2008-07-22 16:24 ` What new libraries or functionality does Guile need? Kjetil S. Matheussen
[not found] <cmu-lmtpd-23333-1216458306-3@mail-imap1.uio.no>
2008-07-19 11:08 ` Kjetil S. Matheussen
2008-07-21 16:02 ` JonWilson
2008-07-22 13:09 ` Bill Schottstaedt
-- strict thread matches above, loose matches on Subject: below --
2008-07-18 19:43 dsmich
2008-07-18 19:37 dsmich
2008-07-18 17:13 Mike Gran
2008-07-18 17:39 ` Julian Graham
2008-07-18 18:32 ` Andre Kuehne
2008-07-19 0:40 ` Jose A. Ortega Ruiz
2008-07-19 5:49 ` Maciek Godek
2008-07-19 18:10 ` Bill Schottstaedt
2008-07-20 20:42 ` Ludovic Courtès
2008-07-20 22:35 ` Mike Gran
2008-07-21 6:34 ` Thien-Thi Nguyen
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=809243.47320.qm@web37901.mail.mud.yahoo.com \
--to=spk121@yahoo.com \
--cc=guile-user@gnu.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).