Linux bluetooth development
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Fredrik Noring <noring@nocrew.org>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] [PATCH] New keytab storage
Date: Sat, 31 Jan 2004 19:01:28 +0100	[thread overview]
Message-ID: <1075572088.2720.59.camel@pegasus> (raw)
In-Reply-To: <1075565012.14644.176.camel@akka.yeti.nocrew.org>

Hi Fredrik,

> > But I think we should discuss some design goals of the new device manager.
> 
> Great idea. What's your plan for it?

one of my big goals is to have a library with a much improved API. This
means that all HCI related functions use the hci_* prefix and follow the
naming scheme from the HCI part of the Bluetooth specification. But the
HCI part should not be used for common applications. These applications
should use bt_* functions that offer an enhanced functionality. For
example setting the local name. The hci_* part only send the HCI
command, while the bt_* stuff also stores the name in a database so it
can be restored after reboot. I think you get the idea.

> > I don't see what kind of mess in "glib-ectomy" you mean, but go ahead
> > and send a patch for it. 
> 
> Some bads, I think:
> 
>   - The API can be improved
>   - Tons of ugly (even in opionon) typedef:s
>   - No style

in the early days the hcid depends on glib and this code is a small
compat layer to be free from the glib. I wrote a similar replacement for
utils2. May you want to take a look at the helper library.

Regards

Marcel




-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

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

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-30 23:56 [Bluez-devel] [PATCH] New keytab storage Fredrik Noring
2004-01-31  0:32 ` Marcel Holtmann
2004-01-31  0:55   ` Fredrik Noring
2004-01-31  1:18     ` Marcel Holtmann
2004-01-31  9:27       ` Fredrik Noring
2004-01-31 15:23         ` Marcel Holtmann
2004-01-31 15:40           ` Fredrik Noring
2004-01-31 15:52             ` Marcel Holtmann
2004-01-31 16:03               ` Fredrik Noring
2004-01-31 18:01                 ` Marcel Holtmann [this message]
2004-01-31 18:15                   ` Fredrik Noring
2004-01-31 10:47   ` 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=1075572088.2720.59.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=noring@nocrew.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