Support for realtime web

[JohannesLichtenberger]

Meaning in a first step we should stream the data changes for a resource to interested clients (we could just stream the JSON we generate, which stores a change track).

In a second step we can support queries, which only query one resource. Thus, naively we'd probably have to execute the query/queries asynchronous once a trx has been flushed to disk and check that only result nodes in the curre transaction intent log are streamed to interested clients. Maybe we can store the compiled query at least up until indexes are added/dropped.

Better ideas are of course welcome. A simpler much more efficient approach would be to check for updates on certain paths in the resource.

[JohannesLichtenberger]

How does RethinkDB implement this?

[mosheduminer]

I wonder if looking at https://github.com/pubkey/event-reduce would be helpful.

[JohannesLichtenberger]

Thanks Moshe, do yohh understand the basic algorithm they are using? Maybe it's too late currently, but I don't get how they determine if a new record from a change event is a query result or not.

[mosheduminer]

I don't know, I haven't really looked at the implementation. So I only know what it says in the readme.