public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] how to get service name and how to connect	through it
Date: Sun, 18 Jun 2006 11:30:32 +0200	[thread overview]
Message-ID: <1150623032.8816.7.camel@localhost> (raw)
In-Reply-To: <a3b1b800606180216r729c9e1fq91f67249b916d968@mail.gmail.com>

Hi Jan,

> i've already written that but I must reiterate that the main
> reason people keep asking is that there's quite a big lack of
> documentation. Even if you just want to write a small utility, you
> have to study quite a lot of source code. Seems to me like some kind
> of sport or what under linux (I'm more of a Windows guy). Or that's my
> point of view at least. I know you try, to me writing a BlueZ app
> seemed much like building a new car from parts where my only reference
> is an already completed car. You can peak inside, see how they did it,
> but in the end, you have to do a lot of tweaking and trying of
> different combinations to make it work. And for example, I never got
> an answer to why the HCI scanning routine (and the hctitool utility =>
> BlueZ) ignores my timeout value...also, there's lots of error codes
> and nobody tells me what went wrong or why.

for this reason we spent quite some time to design the the BlueZ D-Bus
API. It makes it easy to do the basic tasks without knowing any details
about the BlueZ internals or Bluetooth internals like HCI. And you can
use it with C, C++, Python, Java, Mono etc.

Regards

Marcel




_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

      reply	other threads:[~2006-06-18  9:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-14  5:01 how to get service name and how to connect through it Gloria Saripah Patara
2006-06-17 10:27 ` [Bluez-devel] " Marcel Holtmann
2006-06-18  9:16   ` Jan Benes
2006-06-18  9:30     ` Marcel Holtmann [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=1150623032.8816.7.camel@localhost \
    --to=marcel@holtmann.org \
    --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