From: "Heiko Wundram (Beenic)" <wundram@beenic.net>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Using BlueZ in commercial applications - Once again.
Date: Thu, 5 Jul 2007 11:35:23 +0200 [thread overview]
Message-ID: <200707051135.23459.wundram@beenic.net> (raw)
In-Reply-To: <Pine.LNX.4.63.0707051114450.25165@redbean.intranet.gw-instruments.de>
Am Donnerstag 05 Juli 2007 um 11:20:31 schrieb Peter Wippich:
> This is not fully true. You need soem glue layer which needs to be GPL or
> LGPL. Check http://www.tomtom.com/page.php?Page=3Dgpl for examples.
>
> And I think you agree that the Tom Tom Navigation systems are commercial
> products.
Totally true, and that's why I asked about the D-BUS interface because that=
is =
(supposedly, as it's LGPL-licensed) a glue layer which would work for my ca=
se =
(without me having to implement the glue code).
But generally, this means that in case the available glue layers don't fit =
my =
need, I will have to write a glue layer between my commercial application a=
nd =
BlueZ, which not only costs resources and time but also makes the applicati=
on =
more complex (and error-prone, because of blown code size and the need for =
IPC, as wrapping BlueZ in another library would defeat the purpose of the =
GPL-circumventing glue code), which is generally not acceptable for the =
small- to medium-scale fully integrated solution we're currently working on.
And, most importantly, we don't have a team of programmers like TomTom does=
to =
develop this glue.
Anyway, I respect the licensing decision on the BlueZ developers part fully=
, =
which is not what I'm trying to debate about. But, as I said, as long as =
there is no fully functional glue code which works out of the box with =
commercial applications - the socket-API being one form of such glue code =
(but because that requires a GPL'd header to actually function, think of =
AF_BLUETOOTH defined only in bluetooth/bluetooth.h, it's out of the =
question) - BlueZ is simply unusable for our current needs, and I guess qui=
te =
a lot of other commercial Bluetooth developers would feel the same.
Anyway, thanks you two for taking the time to answer me.
-- =
Heiko Wundram
Product & Application Development
-------------------------------------
Office Germany - EXPO PARK HANNOVER
=A0
Beenic Networks GmbH
Mail=E4nder Stra=DFe 2
30539 Hannover
=A0
Fon =A0 =A0 =A0 =A0+49 511 / 590 935 - 15
Fax =A0 =A0 =A0 =A0+49 511 / 590 935 - 29
Mail =A0 =A0 =A0 wundram@beenic.net
Beenic Networks GmbH
-------------------------------------
Sitz der Gesellschaft: Hannover
Gesch=E4ftsf=FChrer: Jorge Delgado
Registernummer: HRB 61869
Registergericht: Amtsgericht Hannover
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-07-05 9:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-04 15:19 [Bluez-devel] Using BlueZ in commercial applications - Once again Heiko Wundram|Beenic
2007-07-05 8:04 ` Marcel Holtmann
2007-07-05 9:08 ` Heiko Wundram (Beenic)
2007-07-05 9:20 ` Peter Wippich
2007-07-05 9:35 ` Heiko Wundram (Beenic) [this message]
2007-07-05 11:04 ` Ranulf Doswell
2007-07-05 12:14 ` Heiko Wundram (Beenic)
2007-07-06 6:00 ` Marcel Holtmann
2007-07-06 10:21 ` Ranulf Doswell
2007-07-06 6:09 ` Marcel Holtmann
2007-07-06 6:44 ` Heiko Wundram (Beenic)
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=200707051135.23459.wundram@beenic.net \
--to=wundram@beenic.net \
--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