Merge pull request #23 from cfsghost/master

Using libuv instead of ev_io, it can support Node.js v8.0+ right now!
Merge pull request #24 from cfsghost/master

Missing files for context loop
Merge pull request #25 from cfsghost/master

Using GYP to be build script instead of wscript
Merge pull request #26 from cfsghost/master

Add EXPAT environment variable to binding.gyp and modify examples
Merge pull request #27 from cfsghost/master

Fixed a bug that hangs when other module needs glib main context as well
Merge pull request #32 from cfsghost/master

Fixed a critical bug that context cause node process uses 100% CPU usage (Closed #31)
Merge pull request #33 from cfsghost/master

pump version and update package.json
Merge pull request #34 from cfsghost/master

Fix typo
Merge pull request #35 from cfsghost/master

Release New version 0.0.8
Fixed decoding of 64 bit integers

It seems that Integer in V8 is limited, on 32 bit version of Node.js, to a 32 bit integer.
With node 0.8.*, an integer overflow occurs when trying to read uint64 types from DBus.

Number, on the other hand, does not seem to have a limit.

I am not sure if this bug would also exist for encoding values, since IntegerValue() is used
there, again for 64 bit integers. 
Merge pull request #37 from Ivshti/patch-1

Fixed decoding of 64 bit integers
Fixed signal handling

In Node-dbus 0.0.8, signals did not appear to be working - at all. It seems that a signal filter
was added only ONCE, which is unacceptable if we have multiple connections (multiple interfaces).
In this case, the filter must be attached for each connection.

So I moved dbus_connection_add_filter to GetInterface
Merge pull request #38 from Ivshti/patch-3

Fixed signal handling
Fixed receiving arguments on services

Seems that this particular piece of code incorrectly assumes args will be an array of arguments,
while the C++ code that translates DBus Messages into V8 objects returns an array
only if there are more than one arguments. When there is only one argument, Array.prototype.slice.call
is incorrectly called on that argument.
The result is chaotic: numbers are not received at all and strings are received one character per argument.
Merge pull request #39 from Ivshti/patch-4

Fixed receiving arguments on services