add push_proxy option

[ddouglascarr]

If I am setting up a database that will have a push and pull replication, I want pouchdb-load to register a checkpoint for push replication as well.

As it currently works, after using pouchdb-load with the proxy option, the pull replication can get going straight away, but the push replication needs to run the checkpointer across the whole database.

This isn't necessary when the database is new and completely populated by load.

[foucdeg]

I'm not sure that I understand the internals, but it would be nice to have that nice proxy speed boost for the push replication too.

[nolanlawson]

@ddouglascarr Hm, that seems kinda odd to me given that pouchdb-load only loads in one direction. :) Instead of using sync(), you could do two separate replicate() commands, and then each one can have their own load() and proxy. Does that make sense? Otherwise I'm not sure what you're asking for here.

BTW on a side note, bulkDocs() has been implemented and should arrive in PouchDB 4.1.0. The CouchDB 1.x implementation is forthcoming, and PouchDB Server will get it as soon as PouchDB does: https://github.com/pouchdb/pouchdb/pull/4169

[ddouglascarr]

@nolanlawson. Thanks for the response. I think I have a use case that might be not the target for the plugin. I'll explain what I'm doing and what I intend to do so that anyone else trying this can use as a reference.

TLDR: no, load() on the server is very inefficient. (would have to generate pouchdb dump on the client and send it back to the server, just to set the checkpoint)

I'll close the issue, as it looks like bulkGet() will replace this anyway.

Scenario:

• I have a couchDB server, from which I generate pouchdb-dump-cli files.
• There are over 1000 documents to be replicated.
• My mobile application downloads these files one at a time and uses pouchdb.load() to populate it's local database.
• It then establishes a push and pull replication to the couchdb server.

Problem:

• The push replication has to start at seq:0 and checkpoint up to the update_seq.
• This shouldn't be necessary, as we know there is nothing new on the local database yet.

Solution:

• Manually create a checkpoint on the couchdb server that has the local update_seq. Record this info in the local database.

If anyone else runs into this problem between now and when bulkGet is usable (unlikely), mention me here and I can help you do it.

[foucdeg]

@ddouglascarr this is my use case too and I'm interested in your solution.

[foucdeg]

@nolanlawson and I do think this is a common use case. I understand that you find it odd to make load() write a checkpoint on the remote, but once @ddouglascarr explains how to do it ourselves, his explanation might be relevant to mention in the readme.

[foucdeg]

Hi @ddouglascarr , sorry to dig this up but I still really need to know how to to manually create the checkpoint on the remote database. Can you please explain it or point me to any instructions ? Thanks