>
>
> The "session" key in the JSON response is not an HTTP session cookie; it's 
> an ID that represents the replication task internally. (The name is 
> confusing, but we didn't make it up; it came from the CouchDB API.)
>
> —Jens
>

Ok understood that thing. 

So now if the auth to SG fails, how i call my function to get a new cookie 
so that sync can continue ?

And any clue why does it work in 1.0.0 and not in 1.0.2 ? (i.e the 
authChallenge handler mentioned in my code)

-- 
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 mobile-couchbase+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/mobile-couchbase/58b132fa-a6b2-4526-80df-a0ddbcad53b1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to