From: "Mikael Lindqvist" <li.mikael.spam@gmail.com>
To: "BlueZ users" <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] permissions to set local name
Date: Tue, 21 Nov 2006 10:14:12 +0100 [thread overview]
Message-ID: <b5dccebe0611210114q57dca584me210abd2a37fc3da@mail.gmail.com> (raw)
In-Reply-To: <1164012204.28397.22.camel@localhost>
Hi,
>
> With the bluez-utils-3.x series, the D-Bus support is required. We don't
> support any non D-Bus version anymore. You will see the long term
> advantage of D-Bus once you start using it. Trust me. I wasn't a believe
> for a long time, but nowadays, D-Bus is the way to go.
>
Ok, I might give D-Bus a chance, but it depends.. :)
Do you know of something that makes it possible to use d-bus to do
obex pushes? I have been looking for that but not found anything. The
reason why I haven't used d-bus for my project before is mainly
because of this, it would feel strange to have half the application
use d-bus and the other half not.
-- Mikael
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2006-11-21 9:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-19 11:50 [Bluez-users] permissions to set local name Mikael Lindqvist
2006-11-19 12:47 ` Marcel Holtmann
2006-11-20 8:31 ` Mikael Lindqvist
2006-11-20 8:43 ` Marcel Holtmann
2006-11-21 9:14 ` Mikael Lindqvist [this message]
2006-11-21 9:17 ` Marcel Holtmann
2006-11-21 9:36 ` Mikael Lindqvist
2006-11-21 11:10 ` Marcel Holtmann
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=b5dccebe0611210114q57dca584me210abd2a37fc3da@mail.gmail.com \
--to=li.mikael.spam@gmail.com \
--cc=bluez-users@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