From: Fabien Chevalier <fabchevalier@free.fr>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] HFP design question : polls opened !
Date: Mon, 08 Oct 2007 17:46:45 +0200 [thread overview]
Message-ID: <470A50E5.2090800@free.fr> (raw)
Dear Bluez friends,
Looks like HFP work will finally get started, thanks to Frederic
Dalleau's initiative. :-)
For my part i will switch to that one day or the other, however at
the moment i am still working on some a2dp fixes and some other stuff,
but i will get there eventually.
One of the painful issues with HFP is the AT commands parsing. I tend to
be a lazy guy and not very interested in writing a parser (hey we are in
21th century now !! :-) )
To ease the pain we could use the brand new GRegex tool, that brings the
power of regular expressions to the glib world. That would meen however
that we would have to port it to eglib first.
I don't know if this is a good idea or not, it's just an idea.
What do you guys think about it?
Cheers,
Fabien
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2007-10-08 15:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-08 15:46 Fabien Chevalier [this message]
2007-10-08 16:50 ` [Bluez-devel] HFP design question : polls opened ! Marcel Holtmann
2007-10-09 8:19 ` Fabien Chevalier
2007-10-09 8:45 ` Marcel Holtmann
2007-10-09 9:43 ` Fabien Chevalier
2007-10-09 10:02 ` Frédéric Dalleau
2007-10-09 10:10 ` 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=470A50E5.2090800@free.fr \
--to=fabchevalier@free.fr \
--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