Updated hashring to 1.0.8 and updated docs about ketama compatibility
Merge pull request #203 from acarrasco/master

fix three tests after #108
Merge pull request #184 from Ryanl92/master

Inconsistent consistent hashing algorithm, not matching libmemcached
[nuke] Remove pointless make file, everything should be done by npm scripts
[pkg] Pre-bump as the previously merged pull request was a major breaking change
[travis] restore travis-ci
[minor] Nuke pointless HTML docs
Revert "Restore the correct domain before calling the user callback"

This reverts commit b9175a2c0c397cf35903fcf7021bacac408b5edc.

Domains have been a common source of problems since I started using them and with
reports of memory leaks that got introduced in the latest version I think it's
save to say that this does not belong in this module and should be solved in
user code instead.

Fixes #186
Workaround an issue in v8 that makes retrieving keys very slow for certain key sizes
Merge pull request #205 from ageitgey/work-around-v8-GC-issue

Workaround an issue in v8 that makes retrieving keys very slow for certain key sizes
tiny text bug
Merge pull request #206 from atomantic/readme

tiny text bug
[minor] Add missing compatiblity options
[minor] Nuke changelog, it's done in github releases from now on.
[fix] Corrected the `compatibility` typo as seen in c6c3ac9f98d910d0846d7fa8fe5f7c5887ff5ec3
Improve libmemcached compatibility.

When using ketama compatibility, utilise the `default_port` option from 3rd-Eden/node-hashring#23
Merge pull request #208 from rcoup/libmemcached-compat

Improve libmemcached compatibility.
[minor] Depend on the latest jackpot, renamed the `default_port` to `default port` #208
[dist] 2.0
Check for statSet length

As I don't know my way round the whole codebase, I've checked for a length greater than one as this covers both the error I was getting on line 623, and a possible(?) undefined value assigned on line 626.

closes #212