From: ludo@gnu.org (Ludovic Courtès)
To: Christopher Baines <mail@cbaines.net>
Cc: guix-devel@gnu.org, guile-user@gnu.org
Subject: Re: Using scheme-memcached with Guile
Date: Fri, 28 Jul 2017 23:29:56 +0200 [thread overview]
Message-ID: <87ziboi71n.fsf@gnu.org> (raw)
In-Reply-To: <20170727191029.27b5e233@cbaines.net> (Christopher Baines's message of "Thu, 27 Jul 2017 19:10:29 +0100")
Hi,
Christopher Baines <mail@cbaines.net> skribis:
> I noticed recently that there is a scheme client for Memcached [1], I
> was looking at how this can be used with Guile, with the intention of
> packaging it for Guix.
Ian Price can probably answer. :-)
There’s also a memcached client in Andy’s Fibers, which might be of
interest:
https://github.com/wingo/fibers/wiki/Manual#Memcached
HTH,
Ludo’.
next prev parent reply other threads:[~2017-07-28 21:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-27 18:10 Using scheme-memcached with Guile Christopher Baines
2017-07-28 21:29 ` Ludovic Courtès [this message]
2017-07-29 18:14 ` Christopher Baines
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=87ziboi71n.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-user@gnu.org \
--cc=guix-devel@gnu.org \
--cc=mail@cbaines.net \
/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).