Re: [Bluez-devel] SCO on bluez : some architectural tips

[Brad Midgley <bmidgley@xmission.com>]

Fabien

> 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, you should have a look at headsetd source.
> I solved this problem there by having headsetd open the sco channel and 
> then hand it over to the application using unix sockets ancillary data. 
> (man 7 unix for more info)

nice... just like a cross-process dup().

if we have two audio clients open, it sounds like they could both hold 
the fd to the sco socket--we'd just have to arbitrate who is allowed to 
use it at any one time.

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