From: Joel Reymont <joelr1@gmail.com>
To: Edgar Friendly <thelema314@gmail.com>
Cc: Gerd Stolpmann <info@gerd-stolpmann.de>,
Mika Illouz <mika@wink.com>, caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] Wink releases caching library
Date: Fri, 9 Nov 2007 23:07:22 +0000 [thread overview]
Message-ID: <9ED9BF56-2719-4BAA-81CF-29E36C4A5C54@gmail.com> (raw)
In-Reply-To: <4734E3E9.3040501@gmail.com>
On Nov 9, 2007, at 10:49 PM, Edgar Friendly wrote:
> I can't find any OCaml client for memcached. If noone interrupts me
> by
> pointing out a client that google didn't find, I think I'll go ahead
> and
> write one and see about comparing Cache with memcached.
That's the essence of my question. I assume it wouldn't have taken
long to write a memcached client but Wink chose to write a less
featured memcached of their own. I really wonder why.
--
http://wagerlabs.com
next prev parent reply other threads:[~2007-11-09 23:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-09 20:32 Gerd Stolpmann
2007-11-09 22:16 ` [Caml-list] " Joel Reymont
2007-11-09 22:49 ` Edgar Friendly
2007-11-09 23:07 ` Joel Reymont [this message]
2007-11-10 5:40 ` Edgar Friendly
2007-11-10 15:07 ` Gerd Stolpmann
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=9ED9BF56-2719-4BAA-81CF-29E36C4A5C54@gmail.com \
--to=joelr1@gmail.com \
--cc=caml-list@inria.fr \
--cc=info@gerd-stolpmann.de \
--cc=mika@wink.com \
--cc=thelema314@gmail.com \
/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