From: Likai Liu <liulk@bu.edu>
To: "SooHyoung Oh" <shoh@duonix.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] PortAudio on ocaml
Date: Mon, 14 Jul 2003 22:12:22 -0400 [thread overview]
Message-ID: <C4EA56AA-B669-11D7-9218-000393C43D24@bu.edu> (raw)
In-Reply-To: <000801c34a69$51f8fec0$fe00a8c0@hama>
On Monday, July 14, 2003, at 08:37 PM, SooHyoung Oh wrote:
>
> I didn't read your message seriously,
> but in my first glance, what you want to seems to be asychroneous
> threads.
> Why don't you use Event module of threads library?
> It's a Concurrent ML.
The implementation is up to the actual PortAudio implementors
themselves, which is different on all the platforms that PortAudio runs
on. They use a callback based API as the common interface that each
PortAudio implementation would follow. I have no say over whether they
should use Event module or otherwise. Event is synchronous. The problem
of wrapping PortAudio callbacks using Event is that callbacks have a
realtime requirement, that is, they're required to finish within a
certain amount of time, so they must be processed right away, unlike
Event that counts on being received at some convenient time. Callbacks
need to return directly to PortAudio for further processing.
Hope this clarifies.
liulk
-------------------
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
next prev parent reply other threads:[~2003-07-15 2:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-14 20:55 Likai Liu
2003-07-15 0:37 ` SooHyoung Oh
2003-07-15 2:12 ` Likai Liu [this message]
2003-07-16 9:55 ` Xavier Leroy
2003-07-16 11:59 ` Likai Liu
2003-07-16 16:57 ` Damien Doligez
2003-07-16 17:46 ` Likai Liu
2003-07-18 13:32 ` Damien Doligez
2003-07-19 13:37 ` Likai Liu
2003-07-22 11:17 ` Damien Doligez
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=C4EA56AA-B669-11D7-9218-000393C43D24@bu.edu \
--to=liulk@bu.edu \
--cc=caml-list@inria.fr \
--cc=shoh@duonix.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