Challenges with watching changefeeds and hooks

[daffl]

#75 introduced somewhat of a fix for the following problem:

When watching RethinkDB changefeeds we were just sending the data we get from the database directly as a real-time event. Unlike a normal method call, this means that the data did not get processed through hooks (specifically after) hooks. The current solution is to run the data manually through the respective methods after hooks.

Potential problems are that there is no way to get the information what original method call caused the change (or if it was a Feathers method call at all). This means that hook.params will be empty (no params.user, params.provider, params.query etc.).

Currently hook.params will be set to { query: {} }

I don't think this is really a fixable issue but will put it here for visibility and probably add that caveat to the docs.

[daffl]

Due to these limitations I'm thinking that for the final release (v1.0) watching changefeeds should be disabled by default pointing out these caveats.

[daffl]

Closing, see #119