Mailing List Archive: Bluetooth OBEX interface

Bluetooth OBEX interface

May 17, 2005, 11:10 PM

Post #1 of 3 (2265 views)

Hello,

a discussion raised a question about what we do if an application wants to send
data to another device using OBEX over Bluetooth.
In GPE we have one application to manage all sorts of bluetooth connections.
This application provides DBus services which are used by applications like
gpe-contacts (to send vCards) or gpe-filemanager (to send files).
For the opposite direction a tool should be able to receive files via OBEX and
offer the user to save these files or to open them with an application
registered for the MIME type of the file.

Do we have any part of this in Maemo? If not - are there any plans to introduce
something like this or is someone working on this?

Greetings

Florian

--
The dream of yesterday Florian Boor
is the hope of today Tel: 0271-771091-14
and the reality of tomorrow. Fax: 0271-771091-19
[Robert Hutchings Goddard, 1904] florian.boor@kernelconcepts.de

6C 44 30 4C 43 20 6B 61 16 07 0F AA E6 97 70 A8

Bluetooth OBEX interface [ In reply to ]

johan.hedberg at nokia

May 18, 2005, 7:21 AM

Post #2 of 3 (2164 views)

Permalink

On Wed, May 18, 2005, Florian Boor wrote:
> Do we have any part of this in Maemo? If not - are there any plans to introduce
> something like this or is someone working on this?

We have osso-gwobex (I'm not sure if it's part of maemo yet, but at
least it's licenced under LGPL). gwobex is a higher level abstraction
library on top of openobex. Currently it supports only client side
functionality (File Transfer and Object Push). E.g. our GnomeVFS OBEX
module uses this library.

The idea is that you would ask btcond (from osso-gwconnect package; not
sure if that is part of maemo yet either) for the RFCOMM device node to
use using D-BUS and then pass that device to gwobex. There are two
method calls provided by btcond for this: rfcomm_connect and
rfcomm_disconnect (com.nokia.btcond service, com.nokia.btcond.request
interface).

Johan

Bluetooth OBEX interface [ In reply to ]

florian.boor at kernelconcepts

May 18, 2005, 1:54 PM

Post #3 of 3 (2174 views)

Permalink

Hello,

Johan Hedberg wrote:

> We have osso-gwobex (I'm not sure if it's part of maemo yet, but at
> least it's licenced under LGPL). gwobex is a higher level abstraction
> library on top of openobex. Currently it supports only client side
> functionality (File Transfer and Object Push). E.g. our GnomeVFS OBEX
> module uses this library.

Very nice, this sounds useful...

> The idea is that you would ask btcond (from osso-gwconnect package; not
> sure if that is part of maemo yet either) for the RFCOMM device node to
> use using D-BUS and then pass that device to gwobex. There are two
> method calls provided by btcond for this: rfcomm_connect and
> rfcomm_disconnect (com.nokia.btcond service, com.nokia.btcond.request
> interface).

I don't think these tools are included at the moment, but i hope someone feels
responsible for this task now :-) It would be really nice to have a simple and
documented interface to use OBEX from applications directly. But the GnomeVFS
OBEX module could be useful for this task too.

Greetings

Florian

--
The dream of yesterday Florian Boor
is the hope of today Tel: 0271-771091-14
and the reality of tomorrow. Fax: 0271-771091-19
[Robert Hutchings Goddard, 1904] florian.boor@kernelconcepts.de

6C 44 30 4C 43 20 6B 61 16 07 0F AA E6 97 70 A8