From: Claudio Takahasi <cktakahasi@gmail.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] DBUS service support - Initial library
Date: Fri, 29 Apr 2005 19:20:54 -0300 [thread overview]
Message-ID: <e1effdeb0504291520167b9bb8@mail.gmail.com> (raw)
In-Reply-To: <1114778617.8836.88.camel@pegasus>
Hi Marcel,
My application will provide a DBUS service and
APIs to alows user mode applications interact
with diferent types of Wireless/Wired connections.
This is the reason to create a BlueZ library based
on pand and hcitool functions. My application should
the able to retrieve bluetooth device information,
including establish connection, disconnect, link
status, new devices/services, ...
The DBUS service will not be provided at BlueZ level.
The current DBUS message in the hcid is used to handle
security/authentication issues. This message has a
different proposal. Therefore, use the same macro
"--enable-dbus" to enable/disable is not a good ideia.
Another important information is: the user mode
application doesn't need root privileges to create
a bluetooth connection, because it will request using
APIs and DBUS service.
Can I create a library in the pand directory and
reuse the common codes?
I suggest a directive like "--enable-panz" because
this library aims provide functions to hide connection
details.
Do you agree?
Regards,
Claudio.
On 4/29/05, Marcel Holtmann <marcel@holtmann.org> wrote:
> Hi Claudio,
>=20
> > Let me try justify why I need a new library.
> > 1. A DBUS app should not contain specific bluetooth/Wi-Fi/GPRS connecti=
on code.
> > In my opinion, it is better abstract the connection details.
> > 2. Features required by DBUS app: signal strength, connection establish=
ment,
> > disconnection, new device notification(search for service
> > frequently), automatic
> > IP assigment(with IP conflict resolution and IP announment),
> > device information,
> > active connections, security info, connection lost, ...
> > All these features should be provided by a BlueZ library. At the
> > moment, pand
> > and hcitool provide part of these. However, they are command line
> > application
> > and a DBUS app should use a workaround approach: "execv" function
> > 3. Consider an embedded device, control connections using a DBUS app
> > is the better way to this task. Execute a command line app is not
> > appropriated
> > to handle this context. An embedded app using wireless connection
> > should abstract connection establishment/control details.
> >
> > This is the scenario that I am working on, if I can't contribute
> > developing this library,
> > I will try move all these required features to DBUS app level without
> > add functions/library
> > to BlueZ.
>=20
> think about adding all you need to pand and then start it for example
> with a --dbus option to activate that service via D-Bus.
>=20
> When writing code use the BlueZ coding style. This means, use tabs. For
> the patches, create them with "cvs diff -u" from the BlueZ CVS and make
> sure that you executed "make maintainer-clean" first.
>=20
> Regards
>=20
> Marcel
>=20
> -------------------------------------------------------
> SF.Net email is sponsored by: Tell us your software development plans!
> Take this survey and enter to win a one-year sub to SourceForge.net
> Plus IDC's 2005 look-ahead and a copy of this survey
> Click here to start! http://www.idcswdc.com/cgi-bin/survey?id=3D105hix
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel
>=20
--=20
_______________________________________
Claudio Takahasi
INdT - Nokia Technology Institute
Phone: +55 81 21223034
Recife - Pernambuco - Brazil
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-04-29 22:20 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-28 20:00 [Bluez-devel] DBUS service support - Initial library Claudio Takahasi
2005-04-29 9:47 ` Marcel Holtmann
2005-04-29 12:26 ` Claudio Takahasi
2005-04-29 12:43 ` Marcel Holtmann
2005-04-29 22:20 ` Claudio Takahasi [this message]
2005-04-30 0:04 ` Marcel Holtmann
2005-05-01 21:16 ` Claudio Takahasi
2005-05-01 23:18 ` Marcel Holtmann
2005-05-02 15:32 ` Claudio Takahasi
2005-05-02 16:24 ` Marcel Holtmann
2005-05-09 21:31 ` Claudio Takahasi
2005-05-11 18:27 ` Marcel Holtmann
2005-05-12 9:00 ` Peter Wippich
2005-05-12 12:41 ` Marcel Holtmann
2005-05-12 16:21 ` Peter Wippich
2005-05-20 21:04 ` Claudio Takahasi
2005-05-23 10:27 ` Marcel Holtmann
2005-05-23 15:02 ` Claudio Takahasi
2005-05-24 9:07 ` Marcel Holtmann
2005-05-25 22:20 ` Claudio Takahasi
2005-05-26 9:08 ` Marcel Holtmann
2005-05-26 21:22 ` Claudio Takahasi
2005-05-26 21:40 ` Marcel Holtmann
2005-05-30 22:42 ` Claudio Takahasi
2005-05-30 23:05 ` Marcel Holtmann
2005-06-03 20:34 ` [Bluez-devel] DBUS service support - poll patch Claudio Takahasi
2005-06-03 20:38 ` Marcel Holtmann
2005-06-03 21:31 ` Claudio Takahasi
2005-06-03 22:10 ` Marcel Holtmann
2005-06-06 13:18 ` Claudio Takahasi
2005-06-14 11:37 ` Claudio Takahasi
2005-06-17 21:59 ` Claudio Takahasi
2005-06-18 23:28 ` Marcel Holtmann
2005-05-12 12:45 ` [Bluez-devel] DBUS service support - Initial library Claudio Takahasi
2005-05-12 16:23 ` Peter Wippich
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=e1effdeb0504291520167b9bb8@mail.gmail.com \
--to=cktakahasi@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.