Api change proposal

[cyberbeat]

Hi,

many bluetooth devices only allow one connection at the time. So obex
data server could be the solution to share a session between multiple
applications. But therefore I propose atomic methods to do operations
on paths like
"retrievefolderlist(path)", because with the current "current-folder-
property" there could be appear problems by concurrency.

For example I would like to use obs for a kde kio-slave. But that is
difficult in current state, because often multiple kio-slaves are
created (although this is also a failure of the kio slave scheduler to
not be able to definde max. instance-count..)

[Tadas Dailyda]

Hi,

Unfortunately sessions can't be shared between applications, because
OBEX protocol allows only one operation at a time. Also imagine such
scenario with one session:
1) app1: go to folder "Pictures"
2) app1: retrieve "Picture1.jpg"
3) app2: go to folder "Video"
4) app1: retrieve "Picture2.jpg" (expected to be in "Pictures" folder)
File not found error at this point!

You just have to accept the fact that most Bluetooth hardware is not
supposed to do a lot of concurrency and OBEX protocol is not supposed to
do any concurrent operations AT ALL.

Sorry for the late reply,
Cheers,
Tadas

[cyberbeat]

Hi, your example is exact the case, why I propose an api change, to
offer atomic operations, so that multiple applications could use the
protocol without interfering each other. I think that should be
possible?

Volker