Rethinkdb doesn't have authentication baked in so you have to lock down the ports and use an ssh tunnel to access it on a remote server. Firebase and Parse server (open source) do pub sub and have auth from the get go
On 7 Aug 2017 5:10 am, "Mark Wieder via use-livecode" < use-livecode@lists.runrev.com> wrote: > On 08/06/2017 05:20 PM, Alex Tweedly via use-livecode wrote: > > If so, do you plan on connecting the DB directly to the open Internet, or >>> use a middleware supplying a REST API for clients? >>> >>> i would presume not. The USP of RethinkDB (at least from my very quick >> skim over the website :-) was the 'push' notification of updates to the >> clients - which would be lost if you used a 'traditional' REST API from the >> end-clients to a server. >> > > Interesting. My take on that is that since it requires an open connection > to the database in order for the notifications to happen, it's more like a > pubsub sort of approach. Which is still a nice touch, but it seems like it > requires either a direct connection to the db or a callback mechanism. And > that is also from a very quick skim of that section of the docs. > > -- > Mark Wieder > ahsoftw...@gmail.com > > _______________________________________________ > 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