Breaking changes: persistent dbus connections and configurable timeouts

[bsphere]

this PR includes some changes and improvements that we needed for using the crate;

• BluetoothSession is used as a persistent connection to dbus, instead of opening a different connection for each method call, the session can be initialized with an optional dbus path, which is added as add_match to the dbus connection (useful for filtering messages that are received via incoming() an example usage is in examples/test5.rs

• the timeout for dbus method calls is passed as an argument, most commands are left with 1000 but some (like connect()) have it exposed all the way to make it controllable by the user.

• BluetoothEvent is an enum for BlueZ events, BluetoothEvent::from() can be used to parse incoming messages into BluetoothEvent. the events that we needed are currently in the enum. usage example is also in examples/test5.rs

• implemented some additional functionality - BluetoothGATTCharacteristic::acquire_write() and BluetoothGATTCharacteristic::acquire_notify() (inspired by code from the somewhere in the repository's issues) and BluetoothDiscoverySession::set_discovery_filter()

[LucaCerina]

+1 on acquire_notify functionality. Notification management is fundamental for any BLE application

[dati91]

Hi there!

Wow, great job!

First of all, I'm not working on this project anymore, so it's really great to see that it's not dead yet :).
And I can't really try it to see that everything is OK, so I have to trust you on that one.
But I went through the code and it looks fine to me 👍.

My only request is that: can you make this into maybe 4-5 (or even more if you see that is necessary) meaningful commits? And also move the revision bump into a separate commit.

I hope that's not too much to ask, because I really love to merge this PR.

[bsphere]

Do you want to change the ownership of this project? We are building an embedded application for the communication between IoT devices on top of it

…

On Wed, Oct 24, 2018, 19:33 Attila Dusnoki ***@***.***> wrote: Hi there! Wow, great job! First of all, I'm not working on this project anymore, so it's really great to see that it's not dead yet :). And I can't really try it to see that everything is OK, so I have to trust you on that one. But I went through the code and it looks fine to me 👍. My only request is that: can you make this into maybe 4-5 (or even more if you see that is necessary) meaningful commits? And also move the revision bump into a separate commit. I hope that's not too much to ask, because I really love to merge this PR. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#21 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AB2LTMj6o5izS97bpKmthE7YG0KWAOp2ks5uoJZQgaJpZM4X2OF7> .

[dati91]

This repository is part of a larger ecosystem for Servo. And I'm not the owner of this project anymore, it's under @szeged now. I'm only maintaining it when necessary.

[bsphere]

I did the rebase, i don't have a version bump commit. is it good enough?

[dati91]

Yes, thanks.

[bsphere]

can you please publish a new version to crates.io ?

[dati91]

It's already published as 0.4.0.