marten-de-vries/pouchdb-seamless-auth

Seamless switching between online (CouchDB) and offline (PouchDB) authentication.

pouchdb-seamless-auth's Issues

Problem with 'replication'

I'm struggling with a couple of issues that aren't working as I expected and so dug into the code a little and noticed a line that will eventually fail at around line 166 & 168 in startReplication.

There is a check to see if replication is needed in a specific direction e.g.
if (remoteDoc._rev > localDoc._rev) {
When a document revision goes from 9-xxxxxxxx to 10-xxxxxxx the checks will give the opposite of what is expected.

It needs a function to extract the revision value and to use that in the compares e.g.

function getRev(doc){
    return parseInt(doc._rev.split('-')[0]);
}
...
if (getRev(remoteDoc) > getRev(localDoc)) {

Figure out Travis problems

Currently the Travis build fails, while it works offline. See: https://travis-ci.org/marten-de-vries/pouchdb-seamless-auth/jobs/102394556

Add fallback mode

For untrusted computers, that works only with the online db. Pretty much the idea described in the warning.

Sounds good...but I don't understand

This sounds great... I just don't understand how to use it! I've looked at the tests and I still don't get it. I'm not really clear on when I use the functions in this library vs the ones in pouchdb-auth. Could you provide some examples?

Here is the sort of use case I am after:

• My user exists on the remote couchdb. I login to my web application, but there is no matching user in the browser's local database, so it checks the remote couchdb, finds the user, and caches it so that next time checking the remote couchdb isn't necessary.
• My user doesn't exist locally or on the remote couchdb. So I create a new one, it gets created on the remote couchdb and on the local one so that next time checking the remote couchdb isn't necessary