From: Gerd Stolpmann <info@gerd-stolpmann.de>
To: Joel Reymont <joelr1@gmail.com>
Cc: Mika Illouz <mika@wink.com>, caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] Wink releases caching library
Date: Sat, 10 Nov 2007 16:07:48 +0100 [thread overview]
Message-ID: <1194707268.19355.63.camel@localhost.localdomain> (raw)
In-Reply-To: <AB85239A-5899-4064-87F0-2AE1D758A1AE@gmail.com>
Am Freitag, den 09.11.2007, 22:16 +0000 schrieb Joel Reymont:
> Gerd,
>
> Why did you guys roll your own instead of using memcached?
We considered using memcached. However, there is no client for OCaml,
and especially no asynchronous client, so we would have had to write
one. I looked at the protocol, and it turned out to be weird, ad-hoc,
and not very extensible. It would have been no fun developing such a
client.
In contrast, for developing our own caching server, it was not necessary
to write any new networking code: By using the SunRPC library of
Ocamlnet we got the whole communication stuff for free, and the protocol
is now well-structured and easily extensible. Furthermore, we could
tailor the features to our requirements, and have the guarantee that we
can adapt the server to any changes.
Actually, we needed only 1 day for developing the library, and another
day for integrating it. This is what other companies spend for
evaluating external software they might want to use. So the costs were
justified, and we now have exactly the software we wanted.
So the essence is: By using good tools (OCaml, Ocamlnet, etc.) we can
develop the software ourselves with the same costs as the integration of
an external component would have taken. Plus, we have perfectly adapted
software, and are on the safe side for the future. Sounds like a good
deal, right?
Gerd
>
> Thanks, Joel
>
> On Nov 9, 2007, at 8:32 PM, Gerd Stolpmann wrote:
>
> > "Cache implements a caching service for storing arbitrary strings that
> > can be located by string keys. The caching service is reachable over
> > TCP. The cache can be distributed over several nodes. The cache can be
> > saved to disk in regular intervals. A client module is included. Both
> > synchronous and asynchronous access methods are defined."
>
> --
> http://wagerlabs.com
>
>
>
> _______________________________________________
> Caml-list mailing list. Subscription management:
> http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list
> Archives: http://caml.inria.fr
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
>
--
------------------------------------------------------------
Gerd Stolpmann * Viktoriastr. 45 * 64293 Darmstadt * Germany
gerd@gerd-stolpmann.de http://www.gerd-stolpmann.de
Phone: +49-6151-153855 Fax: +49-6151-997714
------------------------------------------------------------
prev parent reply other threads:[~2007-11-10 15: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
2007-11-10 5:40 ` Edgar Friendly
2007-11-10 15:07 ` Gerd Stolpmann [this message]
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=1194707268.19355.63.camel@localhost.localdomain \
--to=info@gerd-stolpmann.de \
--cc=caml-list@inria.fr \
--cc=joelr1@gmail.com \
--cc=mika@wink.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;
as well as URLs for NNTP newsgroup(s).