From: Jim Carter <jimc@math.ucla.edu>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Telephony plugin framework
Date: Tue, 22 Apr 2008 11:23:09 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0804221120250.5120@xena.cft.ca.us> (raw)
In-Reply-To: <1208888105.16346.18.camel@greatbear>
On Tue, 22 Apr 2008, Alok wrote:
> 1. 'hcid' maintains a list of 'telephony devices'[a GList]. it also
> exports methods to create, destroy, update these devices.
Sorry, I'm not a regular participant in this thread so I may not be
understanding something: which devices qualify to be "telephony devices"?
Only those that announce availability of a HSP service? Is an A2DP
headphone forever disqualified (unless it has dual HSP capability which
some of them do)?
I assume the SDP thread in hcid will take care of registering the
qualifying devices.
James F. Carter Voice 310 825 2897 FAX 310 206 6673
UCLA-Mathnet; 6115 MSA; 405 Hilgard Ave.; Los Angeles, CA, USA 90095-1555
Email: jimc@math.ucla.edu http://www.math.ucla.edu/~jimc (q.v. for PGP key)
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2008-04-22 18:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-22 18:15 [Bluez-devel] Telephony plugin framework Alok
2008-04-22 18:23 ` Jim Carter [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=Pine.LNX.4.64.0804221120250.5120@xena.cft.ca.us \
--to=jimc@math.ucla.edu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox