Linux bluetooth development
 help / color / mirror / Atom feed
From: Fredrik Noring <noring@nocrew.org>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [gnome-bluetooth] What stuff in gnome-bluetooth does, and ideas for its future
Date: Fri, 30 Jan 2004 21:31:45 +0100	[thread overview]
Message-ID: <1075494705.14644.47.camel@akka.yeti.nocrew.org> (raw)
In-Reply-To: <1075486723.26729.183.camel@pegasus>

Marcel,

fre 2004-01-30 klockan 19.18 skrev Marcel Holtmann:
> This makes you independent from the database format (I prefer
> Berkeley DB at the moment) and you don't need to have database
> code in the Bluetooth library. 

A built-in ASCII table format for all (or most) services is important,
I think, because that's extremely lightweight and efficient for the
common cases. It should be the default.

There can be support for various database client libraries as well
(MySQL, LDAP, Oracle, Berkeley and whatever someone likes). Using any
of those is a matter of:

  1. Linking with the appropriate database client library.
  2. Writing a proper configuration in hcid.conf.

> But when we design it this way, we must make sure that we have the 
> highest security for the link key transactions.

Some database clients support SSL, if that's required. I think such
option ought to be decided by the administrator.

> Additional commands can be NAME or ISPAIRED, but I am also not sure if a
> binary protocol would be better. Maybe we can use D-BUS for it.

Yes, maybe.

> Some other comments from me. I am not going to include such big changes
> into hcid. This is development work for the new security manager or call
> it device manager which is going to replace hcid.

Why? (I'm sure all this can be backwards compatible with current hcid.)
I think it's a good idea to work with the current code base in any case.

> Fredrik, would you please start a new post on the bluez-devel mailing
> list, so we have a new thread for it. This is not really GNOME related
> and I am not a big friend of cross-posting.

Sure! This is technical now.

Fredrik

  reply	other threads:[~2004-01-30 20:31 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1064593223.12843.127.camel@saag>
     [not found] ` <1067882864.15593.326.camel@dhcp-116.surrey.redhat.com>
     [not found]   ` <1067906859.15607.48.camel@saag>
2004-01-28 23:04     ` [gnome-bluetooth] What stuff in gnome-bluetooth does, and ideas for its future Fredrik Noring
2004-01-29  0:50       ` Fredrik Noring
2004-01-29 11:09         ` Edd Dumbill
2004-01-29 15:22           ` Marcel Holtmann
2004-01-29 15:32             ` Edd Dumbill
2004-01-29 18:14               ` Fredrik Noring
2004-01-30 17:45               ` Fredrik Noring
2004-01-30 18:18                 ` Marcel Holtmann
2004-01-30 20:31                   ` Fredrik Noring [this message]
2004-01-29 11:30         ` [Bluez-devel] " Fred Schättgen
2004-01-29 18:44           ` Fredrik Noring
2004-01-29 20:19             ` [Bluez-devel] " Fred Schättgen
2004-01-30 18:10               ` [gnome-bluetooth] " Fredrik Noring
2004-01-30 18:26                 ` Marcel Holtmann
2004-01-30 18:49                   ` Eugene Crosser
2004-01-30 19:06                     ` Marcel Holtmann
2004-01-30 20:41                     ` Fredrik Noring
2004-01-30 20:35                   ` Fredrik Noring
2004-01-30 18:49                 ` [Bluez-devel] name cache Fred Schättgen
2004-01-30 20:54                   ` Fredrik Noring

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=1075494705.14644.47.camel@akka.yeti.nocrew.org \
    --to=noring@nocrew.org \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=marcel@holtmann.org \
    /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