From: Marcel Holtmann <marcel@holtmann.org>
To: jw@stollmann.de, BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] BECI
Date: Tue, 28 Nov 2006 18:53:04 +0100 [thread overview]
Message-ID: <1164736384.13955.24.camel@aeonflux.holtmann.net> (raw)
In-Reply-To: <20061128071440.25196.qmail@bux.stollmann.net>
Hi Juergen,
> BECI is designeated as a Profile orientated Interface situated on top of profiles and protocols
> to interact with aplications.
> So its not a question of hardware.
> However since a working group has not been established yet no specs exist.
I heard about BECI and actually my understanding is that stuff like
L2CAP and RFCOMM can run on the Bluetooth chip itself and doesn't needed
to be implemented in the actual host OS. However my tip is that someone
might simply have a look at our D-Bus based API, because we designed all
methods and signals from the viewpoint of the applications. It has
become one of the easiest to use abstractions, I have seen so far.
Regards
Marcel
-------------------------------------------------------------------------
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-28 17:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-26 20:41 [Bluez-devel] BECI Andreas Merkle
2006-11-28 4:24 ` Marcel Holtmann
2006-11-28 7:14 ` Juergen Wichmann
2006-11-28 17:53 ` Marcel Holtmann [this message]
2006-11-28 22:32 ` Andreas Merkle
2006-11-29 8:16 ` Chafik Moalem
2006-11-29 9:12 ` Marcel Holtmann
2006-11-29 10:50 ` [Bluez-devel] two concurrent a2dp connections Sergey Krivov
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=1164736384.13955.24.camel@aeonflux.holtmann.net \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=jw@stollmann.de \
/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