From: Max Krasnyansky <maxk@qualcomm.com>
To: "Maksim Yevmenkin" <Maksim.Yevmenkin@cw.com>,
"Marcel Holtmann" <marcel@rvs.uni-bielefeld.de>
Cc: "BlueZ Mailing List" <bluez-devel@lists.sourceforge.net>
Subject: RE: [Bluez-devel] Patch for bluez-hcidump-1.5
Date: Mon, 09 Dec 2002 09:58:03 -0800 [thread overview]
Message-ID: <5.1.0.14.2.20021209094932.08533800@mail1.qualcomm.com> (raw)
In-Reply-To: <45258A4365C6B24A9832BFE224837D552B1270@sjdcex01.int.exodus .net>
At 8:7 M 2/7/2002 -0800, Maksim Yevmenkin wrote:
>i will try to make the first step and create hci.h and l2cap.h
>that will contain only HCI and L2CAP types and defines - no system
>specific code. the next step is to define API for Bluetooth sockets
>(HCI and L2CAP), i.e. ioctl names, setsockopt defines etc. i also
>propose to define common libBluetooth, libHCI (and probably libL2CAP)
>API that will hide possible implementation differences. after we
>do that all application just will use defined API and source code
>will be 100% portable.
libL2CAP ?? We don't have libTCP/IP, do we ?
To much abstraction is _bad_.
>as for RFCOMM, SDP etc. then you guys will lead the parade :)
>i'm currently using BlueZ code with the minimal changes. i'm just
>hoping that SDP, RFCOMM etc. implementation won't become too
>Linux specific :)
SDP should be portable.
But RFCOMM TTY stuff will probably be different. How are you going to
implement it btw ?
Max
next parent reply other threads:[~2002-12-09 17:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <45258A4365C6B24A9832BFE224837D552B1270@sjdcex01.int.exodus .net>
2002-12-09 17:58 ` Max Krasnyansky [this message]
2002-12-09 18:37 ` [Bluez-devel] Patch for bluez-hcidump-1.5 Maksim Yevmenkin
2002-12-08 4:17 Maksim Yevmenkin
-- strict thread matches above, loose matches on Subject: below --
2002-12-07 17:07 Maksim Yevmenkin
2002-12-08 0:18 ` Marcel Holtmann
2002-12-07 5:04 Maksim Yevmenkin
2002-12-07 16:01 ` Marcel Holtmann
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=5.1.0.14.2.20021209094932.08533800@mail1.qualcomm.com \
--to=maxk@qualcomm.com \
--cc=Maksim.Yevmenkin@cw.com \
--cc=bluez-devel@lists.sourceforge.net \
--cc=marcel@rvs.uni-bielefeld.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