add API for continuous replications

[gr2m]

I need to create a plugin that syncs all data across all user accounts being created. My idea is to use continuous replications for that. I need filtered replications, as only data shall be synchronised, not tasks.

It's somewhat urgent, so if there is any idea on how to get this working quickly (don't mind dirty), I'm all in for it.

So here's some dream API

var userDb = hoodie.database(userDbName);
var groupDb = hoodie.database(groupDbName);

// create continuous filtered replication userDb => groupDb
groupDb.subscribe(userDb, {filter: filterFunction}, handler);

// create continuous replication groupDb => userDb
userDb.subscribe(groupDb, handler);

// remove replication
userDb.unsubscribe(groupDb, handler);

// continuous replications (aka subscriptions) shall be removed automatically when user accounts get removed.

[gr2m]

@janl @caolan @svnlto

[janl]

assuming low numbers of users this should be fine.

On 03 Feb 2014, at 21:36 , Gregor Martynus [email protected] wrote:

@janl @caolan @svnlto

—
Reply to this email directly or view it on GitHub.

[caolan]

I'm assuming filterFunction is the actual function, not the name of a function in a design doc?

[gr2m]

yes, it's the actual function, would make things so much easier for devs

[caolan]

and as @janl says for a low number of users this should be workable using the replicator db in couch.

[gr2m]

for the case I need this for, there won't be more than 20 users per installation I guess

[janl]

yeah, this is totally fine then. I can build this

[janl]

Related, we should have a replication API that encapsulates a few hoodie specific things like naming conventions, e.g. https://github.com/hoodiehq/hoodie-plugin-global-share/blob/master/worker.js#L376-L393 so plugins get a simple API for setting these things up.

[caolan]

@janl not sure I follow that last comment, how do these things affect replication?

[janl]

@caolan sorry for being dense, doing a brain dump of various things here :)

writing hoodie-plugin-global-shares currently requires intimate knowledge of hoodie conventions (as shown here https://github.com/hoodiehq/hoodie-plugin-global-share/blob/master/worker.js#L376-L393). It would be nice if it would be possible to write this plugins and plugins like it without having to understand the intricate Hoodie-specific naming of databases, documents and properties.

[janl]

(maybe I should open a new issue for this, it just felt related)

[caolan]

@janl yep, we should tidy that up. Open to API suggestions here.