caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Ohad Rodeh" <ORODEH@il.ibm.com>
To: caml-list@inria.fr
Subject: [Caml-list] New Ensemble release, 1.35
Date: Mon, 25 Mar 2002 19:03:13 +0200	[thread overview]
Message-ID: <OF948C5A67.1A1ECC93-ONC2256B87.005D542C@telaviv.ibm.com> (raw)

List,
  A new Ensemble release is now available. As usual, the sources, documentation,
and pre-compiled binaries for windows and linux can be downloaded from
the system's site at www.cs.cornell.edu/Info/Projects/Ensemble.

Ensemble is a group-communication system built in ML, and enjoying performance
equal or superior to similar systems built in C. It also features an extensive C interface.
The system was built in Cornell and the Hebrew universities.

As an aside to recent discussions on the list, I'd be very happy if Caml libraries
were shared libraries, and if exported interfaces (mli) were binary-compatible across
changes in the library internals.

Below the release notes are attached.

--------------------------------------------------------------------------------------------------------------------------

     RELEASE_NOTES  for Ensemble version 1.35

 1. Added a "local" stack, which simply adds property local to vsync.

2. Some slight typing changes in the Hsys module, requested by Roy Friedman.

3. Removed spurious logical-time in outboard mode (HOT). This improves
   line-utilization for HOT applications using outboard mode.

4. Added outboard mode to CE. This allows using Ensemble through a
   server and a thin client library. This is a step forward in the
   rewrite of the HOT interface. Eventually, we intend to completely
   replace it with CE, using a thin overlay layer to mimic HOT semantics.

5. make depend now works on WIN32. The make sequence is now on all platforms:
    for bytecode:
      make depend
      make all
    for optimized code:
      make depend
      make opt

6. Added staggering to the Suspect and Stability layers. This means
   that instead of a flood of messages sent when suspicions and
   stability information is computed, such events are scattered.  This
   prevents implosion at the group leader. This was suggested by Roy Friedman.

7.  Several small bug fixes and cleanup.

OCAML COMPILER VERSION
  We are using version 3.04 for this version.

PORTABILITY
  This version was tested on Linux, and WIN2000.



-----------------------------------------------------------------------------------

Ohad Rodeh
tel: +972-9-9527641
IBM Haifa, storage research



-------------------
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-03-25 17:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-25 17:03 Ohad Rodeh [this message]
2002-07-18  6:45 ` [Caml-list] Problem building -custom on Windows 2000 Friedman Roy
2002-07-18  7:41   ` Jacques Garrigue
2002-07-18  9:26     ` Nicolas Cannasse
2002-07-18 11:12       ` Friedman Roy
2002-07-24 12:13       ` [Caml-list] Has anyone implemented compression in pure OCaml Friedman Roy
2002-07-18  9:52   ` [Caml-list] Problem building -custom on Windows 2000 Xavier Leroy

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=OF948C5A67.1A1ECC93-ONC2256B87.005D542C@telaviv.ibm.com \
    --to=orodeh@il.ibm.com \
    --cc=caml-list@inria.fr \
    /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).