Version française
Home     About     Download     Resources     Contact us    

This site is updated infrequently. For up-to-date information, please visit the new OCaml website at

Browse thread
[Caml-list] extending a type with Marshal
[ Home ] [ Index: by date | by threads ]
[ Search: ]

[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
Date: 2003-10-10 (08:39)
From: skaller <skaller@o...>
Subject: Re: [Caml-list] extending a type with Marshal
On Thu, 2003-10-09 at 07:22, Ker Lutyn wrote:
> Marshal provides a convenient way to pass information between
> components. It requires that types be the same at either end. But for
> multi-machine production systems that must serve traffic continuously,
> you cannot count on upgrading all your systems simultaneously.

If you have p2p connection: Negotiate.
That's the traditional solution: used by modems,
for example.

Fixing a negotiation protocol isn't hard.

IMHO the hard part is identifying 'versions'
and 'capbilities'. Probably the best way is
to use a string encoding (and use a parser).

Nastiest example I can think of is requesting a font.

Note this suggestion requires both servers and clients
to maintain capability to handle several 'old' versions.

This isn't extension of the Marshalled data, rather
quite distinct data for each 'version' is possible,
so the solution seems more general: the cost is extra
handshakes -- how expensive that is depends on how long
the agreement lasts (until explicitly refreshed? until
end of session? only for a single data fetch?)

To unsubscribe, mail Archives:
Bug reports: FAQ:
Beginner's list: