See my responses inline:

On Tuesday, 11 November 2014 14:08:25 UTC-8, Traun Leyden wrote:
>
> See inline responses below:
>
>
>> How can it go back to 2 / 2 changes once it has hit 2 / 3 changes ? 
>>
>>
> That's definitely a bug.  Can you file a github issue here 
> <https://github.com/couchbase/couchbase-lite-java-core> and mention: 
>

> * Is it a pull or push replication? 
>
* Which version of Couchbase Lite are you using?  (or a link to where you 
> downloaded it and I can probably figure out from there)
> * Is this sync'ing with a CouchDB database or a Sync Gateway?
> * Is it possible to put the database or an equivalent database on a public 
> URL so that we can test against it and try to reproduce the issue?
>

I'll try and reproduce the issue to see if it comes up. It may have been 
that push replication surpassed the pull replication at that time, I'll get 
the logs this time.
Most recent version by doing this four days ago.
phonegap plugin remove com.couchbase.lite.phonegap
phonegap local plugin add https:
//github.com/couchbaselabs/Couchbase-Lite-PhoneGap-Plugin.git
I am doing a sync to a sync_gateway
The DB is on a public url, here is the source code:
https://github.com/deefactorial/openmoney-mobile/ 

Let me do some preliminary testing to see if I can reproduce the error and 
I'll create a bug report with the logcat.


 
>
>> The changes feed for documents only sends data when it changes, the 
>> active_tasks is different in that it sends data continuously.
>> When I turn off access to the internet the stream of continuous responses 
>> stops.
>>
>
> I'm not sure I understand this, can you describe it in more details?  Are 
> you saying that the HTTP response never finishes?
>
>  
>
When I get the active_tasks with feed=continuous I get a stream of 
responses, often the data hasn't changed. It will be the same response 
every time, until a document is changed in my local db, Why does it send 
continuous responses when the response data has not changed.
Here is an example log:

11-12 11:58:44.569: I/Web Console(3378): 
task{"progress":100,"target":"https://deefactorial%2B8%40gmail.com:[email protected]:4984/openmoney_shadow/","source":"openmoney","type":"Replication","status":"Processed
 
168 / 168 changes","task":"repl001"} at 
file:///android_asset/www/js/index.js:5861
11-12 11:58:44.569: I/Web Console(3378): push sync connected handler called 
at file:///android_asset/www/js/index.js:5861
11-12 11:58:44.620: I/Web Console(3378): 
task{"progress":100,"target":"openmoney","source":"https://deefactorial%2B8%40gmail.com:[email protected]:4984/openmoney_shadow/","type":"Replication","status":"Processed
 
6 / 6 changes","task":"repl002"} at 
file:///android_asset/www/js/index.js:5861
11-12 11:58:44.620: I/Web Console(3378): pull sync connected handler called 
at file:///android_asset/www/js/index.js:5861
11-12 11:58:44.846: I/Web Console(3378): 
task{"progress":100,"target":"https://deefactorial%2B8%40gmail.com:[email protected]:4984/openmoney_shadow/","source":"openmoney","type":"Replication","status":"Processed
 
168 / 168 changes","task":"repl001"} at 
file:///android_asset/www/js/index.js:5861
11-12 11:58:44.846: I/Web Console(3378): push sync connected handler called 
at file:///android_asset/www/js/index.js:5861
11-12 11:58:44.858: I/Web Console(3378): 
task{"progress":100,"target":"openmoney","source":"https://deefactorial%2B8%40gmail.com:[email protected]:4984/openmoney_shadow/","type":"Replication","status":"Processed
 
6 / 6 changes","task":"repl002"} at 
file:///android_asset/www/js/index.js:5861
11-12 11:58:44.858: I/Web Console(3378): pull sync connected handler called 
at file:///android_asset/www/js/index.js:5861
11-12 11:58:45.124: I/Web Console(3378): 
task{"progress":100,"target":"https://deefactorial%2B8%40gmail.com:[email protected]:4984/openmoney_shadow/","source":"openmoney","type":"Replication","status":"Processed
 
168 / 168 changes","task":"repl001"} at 
file:///android_asset/www/js/index.js:5861
11-12 11:58:45.128: I/Web Console(3378): push sync connected handler called 
at file:///android_asset/www/js/index.js:5861

Notice how all those responses happened within 1 second, and there isn't 
anything new in each of the responses.

I have not seen any responses where the status has been anything but 
"Processed [number] / [number] changes" in the Android version.
When the replication stops (wifi connection disabled) the stream of 
responses stops, there is no response that indicates it has stopped other 
than the stream of responses has stopped.


>> How do I detect the various different states that the replication is in 
>> with the active_tasks API ?
>> Idle when there isn't a change ?
>> Active when changes are not equal ?
>> and Stopped when the stream stops ?
>>
>> How do I know if a change has completed ?
>> do I track the number of changes I have made and compare that to the 
>> number of changes completed ?
>>
>> On Monday, 10 November 2014 11:12:03 UTC-8, Jens Alfke wrote:
>>>
>>>
>>> > On Nov 10, 2014, at 10:56 AM, Dominique <[email protected]> wrote: 
>>> > 
>>> > What I would like to see is access to the Replication Change Listener 
>>> through the REST API, similar to the Document Change Listener. 
>>>
>>> If you add "?feed=continuous" to _active_tasks it'll send push updates 
>>> just like the _changes feed. 
>>>
>>> —Jens 
>>>
>>>  -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Couchbase Mobile" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to [email protected] <javascript:>.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/mobile-couchbase/24bf3b32-bb3a-4df4-ac5e-78481382345d%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/mobile-couchbase/24bf3b32-bb3a-4df4-ac5e-78481382345d%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Couchbase Mobile" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/mobile-couchbase/8dffe823-6a1a-4b6b-8063-c58d6fb0d913%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to