From: Claudio Takahasi <cktakahasi@gmail.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] DBUS service support - Initial library
Date: Mon, 9 May 2005 18:31:55 -0300 [thread overview]
Message-ID: <e1effdeb05050914312761aa57@mail.gmail.com> (raw)
In-Reply-To: <1115051077.21785.133.camel@pegasus>
Hi Marcel,
According with our last discussion. I will to add DBUS service
support in the pand. All code related to DBUS will be added=20
in a new file.
The dbus service will be enabled using the argument "--dbus".
However if this argument is provide with other arguments like
"--connect", "--role" or "--listen" a sharing problem will happen.
What is the behaviour that you want?
1. if "--dbus" was informed no other arguments will be accepted
2. support a shared mode, accepting other arguments.
In this last case, I have to solve a small problem: shared=20
variables, add functions to check the device status,
and common codes like this:
create_connection()
static uint16_t role =3D BNEP_SVC_PANU;=09/* Local role (ie service) */
static uint16_t service =3D BNEP_SVC_NAP;=09/* Remote service */
static int encrypt;
static int secure;
static int master;
static char netdev[16] =3D "bnep%d";
static bdaddr_t src_addr =3D *BDADDR_ANY;
static int src_dev =3D -1;
Regards,
Claudio.
On 5/2/05, Marcel Holtmann <marcel@holtmann.org> wrote:
> Hi Claudio,
>=20
> > After analyze both approachs and consider the future enhancements
> > for BlueZ, implement DBUS service at BlueZ level can be better
> > because it open a new perspective, local services can provided:
> > - dial-up networking
> > - business card exchange
> > - fax
> > - file transfer
> > - headset
> > - audio gateway
> > - ...
> >
> > This is very interesting for embedded environment because
> > only the assigned application will handle the request/notifications.
> >
> > Regarding the service name, I suggest:
> > "org.bluez.pand"
> > Is it fine for you?
>=20
> the name is fine with me.
>=20
> > Do you want a macro to enable this feature at
> > build time?
>=20
> Follow the hcid example. The configure script already detects if D-Bus
> is available or not.
>=20
> Make sure that the current tasks (--connect and --listen) of pand are
> working the same and use --dbus for starting a pand with a D-Bus
> interface.
>=20
> Keep all the D-Bus specific things in a separate files.
>=20
> Regards
>=20
> Marcel
>=20
> -------------------------------------------------------
> 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=3D20
> _______________________________________________
> 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 Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_id=7393&alloc_id=16281&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-05-09 21:31 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
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 [this message]
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=e1effdeb05050914312761aa57@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox