Readme Low level messaging: bus connection example error

[JetForMe]

The docs talk about "dbus.createClient(options)", but the example shows "dbus.createConnection()."

[sidorares]

oops. Do you know which one is correct ( don't have time to read through code right now )

[sidorares]

Any improvements to documentations are very much welcome, if you find time adding something please submit PR

[JetForMe]

Yeah, I don't know which is correct! I'm trying some experiments now. I'm having some issues getting DBus to play nicely in all of a handful of configurations, so I was trying some changes. I think createConnection() is right.

[sidorares]

they both are correct, that was probably not a good choice of names

https://github.com/sidorares/node-dbus/blob/master/index.js#L129-L132

'connection' is for low level messaging - conn.message({...}) and conn.on('message, ...)'

'client' handles RPC-style calls by remembering association from serial/replySerial to callback

[sidorares]

and you can always access connection from a client:

var bus = require('dbus-native').systemBus(); // "client"
bus.connection.message({ body: 'hello', signature: 's'}); 

[JetForMe]

Heh. I find this all very confusing. I'm using DBus to communicate between a C++ app and my node.js app, on both OS X and Debian. During development, I want to be able to launch one or the other, or both, in any order, and I want them to quickly connect or abandon a connection attempt and connect later. I wish I could do this without dbus-daemon running at all, but that doesn't seem to be the case.

[sidorares]

this module allows to communicate directly - you could pretend that you are daemon and point C++ app to your node app by setting DBUS_SESSION_BUS_ADDRESS

[JetForMe]

But it seems I have to create a socket somewhere.