From: Brad Midgley <bmidgley@xmission.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] SCO on bluez : some architectural tips
Date: Thu, 16 Nov 2006 14:56:29 -0700 [thread overview]
Message-ID: <455CDE8D.4010009@xmission.com> (raw)
In-Reply-To: <455CCAF4.8020007@silicom.fr>
Fabien
> Due to this, i had to fall back on having the SCO file descriptor
> available in application process space.
If it's inevitable, I think we could keep the fd in the audio app's
userspace and mostly pull things off as envisioned. We would have to put
in some locking to keep applications from trying to open more
simultaneous sco sockets. I wonder how the other audio servers avoid
this problem.
Brad
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-11-16 21:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-16 20:32 [Bluez-devel] SCO on bluez : some architectural tips Fabien Chevalier
2006-11-16 20:38 ` Albert Huang
2006-11-17 6:46 ` [Bluez-devel] RE : " Frederic Dalleau
2006-11-18 10:02 ` [Bluez-devel] " Fabien Chevalier
2006-11-16 21:56 ` Brad Midgley [this message]
2006-11-18 10:07 ` Fabien Chevalier
2006-11-19 5:45 ` Brad Midgley
2006-11-19 17:02 ` Fabien Chevalier
2006-11-17 6:45 ` [Bluez-devel] RE : " Frederic Dalleau
2006-11-18 10:27 ` Fabien Chevalier
2006-11-18 11:44 ` [Bluez-devel] RE : " Frederic Dalleau
2006-11-19 5:30 ` Brad Midgley
2006-11-19 16:54 ` Fabien Chevalier
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=455CDE8D.4010009@xmission.com \
--to=bmidgley@xmission.com \
--cc=bluez-devel@lists.sourceforge.net \
/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.