Hi Richard ..... like Alex said, there is no Rest api for RethinkDB. The folks at RethinkDB didn't want to expose the whole query language using a rest api, (if i recall correctly they said it is too powerful to do so)...so the driver only accepts queries via driver port and streams resulting json and updates back to client.
My desktop client will connect to a local database which (will or can be part) of a distributed cluster. On Mon, Aug 7, 2017 at 10:53 AM, Bob Sneidar via use-livecode < use-livecode@lists.runrev.com> wrote: > I was thinking the same thing. This isn't a database function per se, it's > more like a sockets function. > > Bob S > > > > On Aug 5, 2017, at 16:42 , Tom Glod via use-livecode < > use-livecode@lists.runrev.com> wrote: > > > > If you go to this page ..... the specs say that it all happens through an > > tcp/ip connection where you make a connection, serialize the query and > > send it .... the db driver port receives queries, and streams data from > > the db via the TCP/IP back to "subscribed" client. > > > > So it doesn't really need to have anything to do with the current > > revdatabase functions....which the posts seem to be talking about. I'm > not > > asking for a rewrite of db layer. > > > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode > _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
