caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Ohad Rodeh" <ORODEH@il.ibm.com>
To: "John Gerard Malecki" <johnm@artisan.com>
Cc: caml-list@inria.fr
Subject: RE: Re[2]: [Caml-list] OcamlSpread 0.0.1 released
Date: Wed, 18 Sep 2002 09:13:48 -0700	[thread overview]
Message-ID: <OF88F8F4FC.1A2E52F0-ON88256C38.005350EC@telaviv.ibm.com> (raw)

I'm the maintainer of Ensemble, so my judgement on which system is better
is of
course subjective. Having said that, I'll try to fairly describe what
Ensemble and
Spread can do.

Generally speaking, they are the same. Both provide group-communication to
users.

Spread splits functionality between a client process, and a server (daemon)
process.
The daemon process needs to run on every machine where there are clients.
User-applications link with the client library, and send/receive messages
through the
local daemon process.

Ensemble allows both client/server, and in-server applications, so that one
can also
write the applications to work as part of the server main-loop. Since
group-communication
applications are normally event-driven, linking into an existing main-loop
should not be
a problem.

Both systems support secure groups, though they have different models for
this. As an
aside, Ensemble intends to move from using OpenSSL to Xavier's cryptokit.

Ensemble splits the "server" into many small layers, where each layer is a
state-machine.
An Ensemble stack is, much like the OS communication stack, a set of layers
stacked on
top of each other. An Ensemble endpoint uses a stack to send/receive
messages. The
set of layers in the stack determine what guaranties are provided:
reliability, flow-control,
packet fragmentation, etc. Users can write they own layers, and there is a
lot of investment
in allowing users to dynamically switch layers on the fly, add new layers,
and debug them.
Equivalent functionality does not exist in Spread.

Ensemble also allows reliable point-to-point messaging, in the context of a
group. This
is similar toTCP, though with somewhat stronger guaranties.

In general, if you want to write an application that does not heavily use
group-communication,
you probably don't care so much about which system to use. If you'd like to
modify the system,
or write something really efficient, I'd suggest using Ensemble.

      Ohad.
-----------------------------------------------------------------------------------

Ohad Rodeh
tel: +972-3-6401641
IBM Haifa, storage research


                                                                                                                                       
                      John Gerard                                                                                                      
                      Malecki                  To:       "Yurii A. Rashkovskii" <yrashk@openeas.org>                                   
                      <johnm@artisan.co        cc:       Ohad Rodeh <orodeh@alum.cs.huji.ac.il>                                        
                      m>                       Subject:  RE: Re[2]: [Caml-list] OcamlSpread 0.0.1 released                             
                                                                                                                                       
                      18/09/2002 06:43                                                                                                 
                      Please respond to                                                                                                
                      "John Gerard                                                                                                     
                      Malecki"                                                                                                         
                                                                                                                                       
                                                                                                                                       



Yurii A. Rashkovskii wrote (2002-09-18T12:16:01+0300):
 >
 > I know about Ensemble, and even use it now. OcamlSpread was an old
 > library and I just decided to release it to public (may be somebody
 > will need it :-) )

Hello Yurii (and Ohad),

Just out of curiosity, and without wanting to start any public
controversy, I was wondering about the differences between Spread and
Ensemble?  (Except for implementation language they seem similar.)
Are there applications where one would be preferable to the other?




-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners


             reply	other threads:[~2002-09-18 16:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-18 16:13 Ohad Rodeh [this message]
2002-09-18 16:36 ` Re[4]: " Yurii A. Rashkovskii
  -- strict thread matches above, loose matches on Subject: below --
2002-09-20 16:14 MONIN Jean-Francois FTRD/DTL/LAN
2002-09-20 16:18 ` Re[2]: " Yurii A. Rashkovskii
2002-09-17 20:06 Ohad Rodeh
2002-09-18  9:16 ` Re[2]: " Yurii A. Rashkovskii

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=OF88F8F4FC.1A2E52F0-ON88256C38.005350EC@telaviv.ibm.com \
    --to=orodeh@il.ibm.com \
    --cc=caml-list@inria.fr \
    --cc=johnm@artisan.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).