caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "SooHyoung Oh" <shoh@duonix.com>
To: "Nick Name" <nick.name@inwind.it>, <caml-list@inria.fr>
Subject: Re: [Caml-list] Asynchronous communication channels
Date: Mon, 9 Jun 2003 08:40:54 +0900	[thread overview]
Message-ID: <004001c32e17$67aa85e0$fe00a8c0@hama> (raw)
In-Reply-To: <20030609001529.53e57c9a.nick.name@inwind.it>

Please check CML (Concurrent ML) in http://cml.cs.uchicago.edu/ .
Event module in ocaml  has the similiar functionality with CML.

And you can find some examples in my web
http://www.duonix.com/~shoh/ocaml/concurrent.html .

Good luck to you.

---
SooHyoung Oh
----- Original Message -----
From: "Nick Name" <nick.name@inwind.it>
To: <caml-list@inria.fr>
Sent: Monday, June 09, 2003 7:15 AM
Subject: [Caml-list] Asynchronous communication channels


> I need some asynchronous channels in my current project. Some of those
> have to block when the maximum capacity is exceded, others are
> one-position buffers wich should have overwrite semantics. Are there
> already done libraries or should I roll my own?
>
> If I have to implement the buffer myself, what's the best way, a buffer
> thread wich uses the Event module or rewriting everything from scratch
> with condition variables to spare a thread?
>
> Thanks for attention
>
> Vincenzo
>
> -------------------
> 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
>

-------------------
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:[~2003-06-08 23:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-08 22:15 Nick Name
2003-06-08 23:40 ` SooHyoung Oh [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='004001c32e17$67aa85e0$fe00a8c0@hama' \
    --to=shoh@duonix.com \
    --cc=caml-list@inria.fr \
    --cc=nick.name@inwind.it \
    /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).