caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Rich Neswold <rich.neswold@gmail.com>
To: Goswin von Brederlow <goswin-v-b@web.de>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Smart ways to implement worker threads
Date: Thu, 15 Jul 2010 10:58:23 -0500	[thread overview]
Message-ID: <AANLkTilJUmUCQx2DiomhBNZdWEUinjnLeu2rFMMwcZ02@mail.gmail.com> (raw)
In-Reply-To: <87sk3mcaeq.fsf@frosties.localdomain>

[-- Attachment #1: Type: text/plain, Size: 1685 bytes --]

On Wed, Jul 14, 2010 at 11:09 AM, Goswin von Brederlow <goswin-v-b@web.de>wrote:

> 4) Do some magic with Event.t?
>
> Problem: never used this and I could use a small example how to use
> this.
>

Event.t (and its associated library) *is* magical in that it provides an
absolutely beautiful concurrent programming model. Forget about select() and
mutexes and other ugly threading concepts. Event.t and friends is how it
should be done.

John H. Reppy's "Concurrent Programming in
ML<http://sharingcentre.net/87081-concurrent-programming-ml.html>"
provides a thorough understanding of how to use this module effectively.
This book presents the material in a very understandable
way: deficiencies in current threading models are discussed as well as how
CML solves the limitations and constraints. The book can be purchased or
downloaded free online.

The few applications I've written that use CML, I found it was more than
sufficient (speed-wise). Whether your application is more demanding, I can't
tell.

Hopefully someone on the list with more experience can comment whether there
are caveats (performance-related or others) in OCaml's support of CML. If
there are, there should be an effort in fixing the problems (I would help in
any way I could.) I'd also recommend incorporating Satoshi Ogasawara's
Concurrent
Cell <http://caml.inria.fr/cgi-bin/hump.en.cgi?contrib=654> project into the
standard library. (This project adds IVars and MVars and other constructs
described in John H. Reppy's book, but not available in the OCaml standard
library.)

Hope this helps!

-- 
Rich

Google Reader: https://www.google.com/reader/shared/rich.neswold
Jabber ID: rich@neswold.homeunix.net

[-- Attachment #2: Type: text/html, Size: 2811 bytes --]

  reply	other threads:[~2010-07-15 15:58 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-14 16:09 Goswin von Brederlow
2010-07-15 15:58 ` Rich Neswold [this message]
2010-07-15 16:19   ` [Caml-list] " David McClain
2010-07-15 17:16   ` Ashish Agarwal
2010-07-15 18:24   ` Goswin von Brederlow
2010-07-15 18:37     ` David McClain
2010-07-15 18:40     ` David McClain
2010-07-15 19:56     ` Rich Neswold
2010-07-16  4:02       ` Goswin von Brederlow
2010-07-16  4:23         ` Rich Neswold
2010-07-16 13:02           ` Goswin von Brederlow
2010-07-16 14:40             ` Dawid Toton
2010-07-16 16:18             ` [Caml-list] " Rich Neswold
2010-07-17 17:53               ` Eray Ozkural
2010-07-20  4:54             ` Satoshi Ogasawara
2010-07-17 18:34         ` Eray Ozkural
2010-07-17 19:35           ` Goswin von Brederlow
2010-07-17 22:00             ` Eray Ozkural
2010-07-15 16:32 ` Romain Beauxis
2010-07-15 17:46   ` Goswin von Brederlow
2010-07-15 18:44     ` Romain Beauxis
2010-07-16  3:52       ` Goswin von Brederlow
2010-07-16  4:19         ` Romain Beauxis
2010-07-16 13:05           ` Goswin von Brederlow
2010-07-16 13:20             ` Romain Beauxis
2010-07-17  9:07               ` Goswin von Brederlow
2010-07-17 13:51                 ` Romain Beauxis
2010-07-17 14:08                   ` Goswin von Brederlow
2010-07-17  9:52 ` Goswin von Brederlow
2010-07-17 14:20   ` Romain Beauxis
2010-07-17 15:52     ` Goswin von Brederlow

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=AANLkTilJUmUCQx2DiomhBNZdWEUinjnLeu2rFMMwcZ02@mail.gmail.com \
    --to=rich.neswold@gmail.com \
    --cc=caml-list@yquem.inria.fr \
    --cc=goswin-v-b@web.de \
    /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).