You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You probably shouldn't use the HTTP API provided by RethinkDB.
It's not secured at all -- it's used only by the web interface because the web interface is supposed to run only on trusted networks. You probably want to build a simple server that will forward the queries to the database.
If you still need it, the protocol currently uses the Buffer class provided by browserify.
The reason why I didn't build an HTTP API in rethinkdbdash is to keep the code clean.
I didn't want having to check everywhere which protobuf library I was using. I also didn't want to have browserify as a dependency.
I'm not quite sure what's the encoding for the JSON API will be, but probably UTF8.
I plan to completely remove protobuf from rethinkdbdash for 1.13.
For my RethinkDB usecase, use over HTTP is an important characteristic, and I am willing to build a HTTP API client for rethinkdbdash.
Currently, I need to know modifications need to be made to rethinkdbdash?
The only other queries I currently have are:
The text was updated successfully, but these errors were encountered: