From: Brad Midgley <bmidgley@xmission.com>
To: Fabien Chevalier <fabchevalier@free.fr>,
BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] combining libalsa & dbus
Date: Thu, 10 May 2007 13:21:22 -0600 [thread overview]
Message-ID: <464370B2.40303@xmission.com> (raw)
Fabien,
I hope you're having a nice break from your hobby stuff. Can I ask you
to think about it a little bit to work through something? You've worked
with the alsa plugin api well enough to maybe help with a problem...
Marcel wants a reworked alsa plugin to go into bluez utils, but it needs
to be a proper dbus client. That would mean the dbus calls would have to
be self-contained right in the alsa plugin. Do you think we could pull
that off? I'm worried that the nature of the calls into the plugin would
make it impossible to have it also listening to dbus.
On top of everything else, Marcel prefers multiprogramming to be done
via select(), nonblocking calls, etc and not threads.
Any ideas?
Brad
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2007-05-10 19:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-10 19:21 Brad Midgley [this message]
2007-05-11 8:26 ` [Bluez-devel] combining libalsa & dbus Marcel Holtmann
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=464370B2.40303@xmission.com \
--to=bmidgley@xmission.com \
--cc=bluez-devel@lists.sourceforge.net \
--cc=fabchevalier@free.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.