From: Denis KENZIOR <denis.kenzior@trolltech.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Suggesting bluez_pinhelper
Date: Tue, 29 May 2007 07:11:56 +1000 [thread overview]
Message-ID: <200705290711.56349.denis.kenzior@trolltech.com> (raw)
In-Reply-To: <200705281848.09618.dgollub@suse.de>
Daniel,
What are your plans with kdebluetooth? Are you going to make KDE3 based
releases or wait until KDE4? I'm asking since Qtopia Bluetooth is Qt4 based
and uses Qt DBUS bindings internally to communicate with BlueZ.
> I have to take a deeper look on the implementation of the BlueZ DBUS
> interface... is there any plan to wrap also BlueZ Service APIs like the
> Input Service? Or is this already done?
>
Yes, we're planning Input service for 4.4 and PAN for 4.4. Actually services
are probably the least useable by KDE the way they are now. Mostly because
we use our own IPC mechanisms, they could probably be easily adapted to any
IPC mechanism though.
> Or you going to implement the Authorization Agent as well?
Yes, this only went non-experimental as of 3.10.1, so we're probably going to
add this in 4.4.
>
> Actually i plan to implement all the services which are available by BlueZ
> ... So it would be very interesting which BlueZ services get
> implemented/used by Qtopia. Or should it be possible to make use of all
> services via
> QBluetoothAbstractService?
The QBluetoothAbstractService is more of a framework class, to help build
service implementation and insure certain features are supported (starting /
stopping services mostly) To use a service you still need to use an
interface class, very similar to BlueZ.
>
> On which version of BlueZ will be Qtopia 4.3 based? bluez-utils 3.9 like
> Qtopia 4.2?
This is the most likely case.
>
> Are you going to keep the OBEX support or make use of the BlueZ transfer
> service in the future?
OBEX support in 4.2 is not that great, we improved it considerably in 4.3. It
wraps OpenOBEX, but makes it very easy to use. We're planning to implement
FTP, PUSH, BPP and BIP profiles over OBEX using this infrastructure. Some
(PUSH client/server, FTP client) are already done.
>
> A separated package would be great...
OK will try prioritize this :)
Regards,
-Denis
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-05-28 21:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-27 13:52 [Bluez-devel] Suggesting bluez_pinhelper Gilboa Davara
2007-05-27 16:36 ` Marcel Holtmann
2007-05-27 17:28 ` Gilboa Davara
2007-05-27 18:04 ` Marcel Holtmann
2007-05-27 18:35 ` Gilboa Davara
2007-05-28 8:29 ` Marcel Holtmann
2007-05-27 16:59 ` Petteri Räty
2007-05-27 17:31 ` Gilboa Davara
2007-05-27 17:48 ` Petteri Räty
2007-05-27 18:41 ` Gilboa Davara
2007-05-29 11:27 ` Stefan Seyfried
2007-05-29 12:45 ` Gilboa Davara
2007-05-27 23:19 ` Daniel Gollub
2007-05-27 23:39 ` Denis KENZIOR
2007-05-28 16:48 ` Daniel Gollub
2007-05-28 21:11 ` Denis KENZIOR [this message]
2007-05-28 22:21 ` Daniel Gollub
2007-05-28 8:29 ` Marcel Holtmann
2007-05-28 16:53 ` Daniel Gollub
2007-05-29 3:50 ` 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=200705290711.56349.denis.kenzior@trolltech.com \
--to=denis.kenzior@trolltech.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