caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Francois Rouaix" <francois@rouaix.org>
To: "Joel Reymont" <joelr1@gmail.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Ensemble dying?
Date: Thu, 22 Feb 2007 19:00:53 -0800	[thread overview]
Message-ID: <f2d6cc680702221900gf94f58csf31ae5883f186b5b@mail.gmail.com> (raw)
In-Reply-To: <7ABF8B9F-46C3-4489-9B02-799CE9C059A9@gmail.com>

It seems that the community where Ensemble originated is now going a
different direction. If you look at Ken Birman's page at
http://www.cs.cornell.edu/ken/, it mentions that his group is working
on a fourth generation of middleware platform based on pubsub. From
where I sit, pubsub based approachs seems closer to current industry
practice.


On 2/22/07, Joel Reymont <joelr1@gmail.com> wrote:
> Folks,
>
> Is anyone using Ensemble? Has anyone used it before?
>
> It seems to be dead and not maintained anymore. I tried posting to
> the list and emailing the maintainer directly but received no response.
>
> I'm wondering if it's something worthy of taking over since it's
> written in OCaml or if I should forget about it and go with Spread
> [1] instead. I couldn't find recent bindings for Spread either,
> except for something from 2002.
>
>         Thanks, Joel
>
> [1] http://www.spread.org
>
> --
> 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
>


      reply	other threads:[~2007-02-23  3:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-22 19:10 Joel Reymont
2007-02-23  3:00 ` Francois Rouaix [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=f2d6cc680702221900gf94f58csf31ae5883f186b5b@mail.gmail.com \
    --to=francois@rouaix.org \
    --cc=caml-list@inria.fr \
    --cc=joelr1@gmail.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).