Michael Aufreiter

Here's a related thread helping explain Dar workflows (with reproducibility in mind): https://github.com/substance/dar/issues/4

Yeah, I'm aware of that. However with Data.js, there's a focus on a stripped down lightweight API. It deliberately breaks with existing standards, such as RDF or JSON-Id. We don't...

Hi! Good points. The addition of a realtime (push) mode is on the list for 0.3 (0.4 at the latest). We're going to introduce swappable transport modes (Websockets, if available...

I'm currently hacking on this. The API I have in mind looks like this: ``` graph.watch("task_updates", {"type|=": "/type/task", "project": "/project/foo"}, function(err, nodes) { // Update the UI appropriately as nodes...

The first parameter is a unique name for the watcher. You can use it to unbind your registration. `graph.unwatch('task_updates')` Also when you call `watch` a second time using the same...

Actually, I think we don't really need RMI at all. Maybe we should consider using Socket.IO directly, keeping dependencies to a minimum and reducing overhead. Nowjs was just the easiest...

Shifted to 0.5.0

I'm working on a full rewrite of the the CouchAdapter that will be ready with Data.js 0.3.0. The current adapter is just a rough implementation to test the API against....

Hey. The exporter service needs to be moved to our new server... will do that asap.

Not yet, since Data.js does some post-processing/filtering on the view results. Thus Couch should ideally run on the same machine (or network) for performance reasons.