Mike Mintz

@mividtim I agree this would be complicated to implement with joins. Are you thinking maybe we'd only do this on queries that follow a formulaic syntax like `r.table(...).filter(...).orderBy(...).limit(...)` and require...

Nothing jumps out immediately as a possible reason to me. When you say "sometimes 100% of the time", does that mean you have a situation that you can reproduce where...

I'm happy to merge in this fix (or accept any PR), but I'm concerned that the error is still happening even after this fix. @coffenbacher or @JerryGreen, have you tried...

Yeah it's not a good long term solution (other than for clients like react-native that don't support binary), but it'll help pin down this bug. Performance wise, it should use...

Good catch! Feel free to open a PR removing the second line.

Yes, see the bottom of the "involved example" on the readme ``` js var app = express(); app.use('/', express.static('assets')); var httpServer = http.createServer(app); options.httpServer = httpServer; options.httpPath = '/rethinkApi'; RethinkdbWebsocketServer.listen(options);...

I agree with @coffenbacher answer: relying on authKey or username/password to secure the connection to the db is not recommended. However, if someone has a use case, e.g. connecting to...

@babakness I'm not sure exactly what's happening, but you should be aware there are often two connections: 1) a proxied connection from the browser via rethinkdb-websocket-server to rethinkdb (which is...

So in order to implement this, we would have to modify the the client handshake to include authentication details. Here are some references: * [Current rethinkdb-websocket-server client handshake code](https://github.com/mikemintz/rethinkdb-websocket-server/blob/master/src/Connection.js#L179-L185) *...

I feel like that `net.js` file shouldn't affect proxied connections. Are you saying that authentication works when you do this? Regarding V0_4 vs V1_0, those are protocol versions. Take a...