From: Richard Jones <rich@annexia.org>
To: Dario Teixeira <darioteixeira@yahoo.com>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Long-term storage of values
Date: Fri, 21 Mar 2008 15:24:08 +0000 [thread overview]
Message-ID: <20080321152408.GB29482@annexia.org> (raw)
In-Reply-To: <905079.47901.qm@web54602.mail.re2.yahoo.com>
On Fri, Mar 21, 2008 at 02:37:28PM +0000, Dario Teixeira wrote:
> If I remember correctly, the model with XDR+rpcgen is that the data type
> is defined in a special XDR notation, which ocamlrpcgen will then use to
> generate the Ocaml type and the (de)serialisation functions.
That's right. You write a '*.x' file and it gets converted to C by
rpcgen or to OCaml by ocamlrpcgen. There's a very lengthy example I
wrote below. XDR is regarded as a rather "old" protocol and support
is somewhat limited (basically, C, Java and OCaml). On the other hand
it is well-understood and miles faster than anything else, since it's
a simple marshalling format just like OCaml's Marshal.
http://git.et.redhat.com/?p=libvirt.git;a=blob_plain;f=qemud/remote_protocol.x;hb=HEAD
> Though XDR
> offers a fairly rich type set, it's not quite as versatile as Ocaml's.
> I just wonder if this will lead to situations where one would rather
> write the (de)serialisation functions by hand instead of relying on
> the poorer expressiveness of the automatic generators.
The limited type set is an advantage if you're sharing data with other
languages (or if you're using C), but a disadvantage otherwise.
> Btw, do you have any numbers concerning XDR performance? My guess
> is that this would be the fastest method after Marshalling.
There's a really tiny table at the end of this document, comparing it
to XML so not really any competition:
http://et.redhat.com/~rjones/secure_rpc/
Rich.
--
Richard Jones
Red Hat
next prev parent reply other threads:[~2008-03-21 15:24 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-28 18:41 Dario Teixeira
2008-02-28 20:01 ` [Caml-list] " David MENTRE
2008-02-28 20:01 ` Thomas Fischbacher
2008-02-28 20:05 ` Mathias Kende
2008-02-28 22:09 ` Basile STARYNKEVITCH
2008-02-29 14:45 ` Martin Jambon
2008-02-29 19:09 ` Jake Donham
2008-02-28 23:42 ` Erik de Castro Lopo
2008-02-29 1:14 ` Brian Hurt
2008-02-29 7:40 ` Gabriel Kerneis
2008-02-29 10:19 ` Berke Durak
2008-02-29 18:05 ` Markus Mottl
2008-02-29 11:44 ` Richard Jones
2008-02-29 14:09 ` Brian Hurt
2008-03-01 14:15 ` Dario Teixeira
2008-03-20 21:03 ` Dario Teixeira
2008-03-20 21:32 ` Martin Jambon
2008-03-20 22:41 ` Dario Teixeira
2008-03-20 23:00 ` Martin Jambon
2008-03-21 14:01 ` Dario Teixeira
2008-03-21 14:28 ` Martin Jambon
2008-03-21 14:34 ` Martin Jambon
2008-03-20 21:42 ` Daniel Bünzli
2008-03-20 22:33 ` Dario Teixeira
2008-03-20 21:43 ` Gerd Stolpmann
2008-03-21 14:37 ` Dario Teixeira
2008-03-21 15:24 ` Richard Jones [this message]
2008-03-22 12:14 ` David MENTRE
2008-03-21 16:04 ` Gerd Stolpmann
2008-03-21 10:32 ` Berke Durak
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=20080321152408.GB29482@annexia.org \
--to=rich@annexia.org \
--cc=caml-list@yquem.inria.fr \
--cc=darioteixeira@yahoo.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