> On Feb 2, 2018, at 9:58 AM, James Nocentini <[email protected]> wrote:
> 
> (Incidentally, speaking of documentation, there appear to be a couple of 
> notable errors in the setup guide for SG 1.5 relating to support for CBL 2.0 
> replication. I submitted feedback via the page; see 
> https://issues.couchbase.com/browse/DOC-3194.) 
> 
> @Ben Thanks for letting us know! That should be fixed now 
> https://developer.couchbase.com/documentation/mobile/1.5/guides/sync-gateway/config-properties/index.html#1.5/databases-foo_db-unsupported.

Hi James,

Part of it is fixed -- the default now reads 'false' rather than 'true'. 
However, the interoperability statement is still apparently wrong.

It reads:

> Note that if this property is set to true, Sync Gateway will no longer accept 
> incoming requests from clients running the 1.x implementation. This includes 
> Couchbase Lite 1.x and CouchDB-based databases (such as PouchDB and Cloudant).

We turned on the `unsupported.replicator_2` setting, and SG appears to be 
working just fine with Couchbase Lite 1.x clients.

The passage I quoted above is directly at odds with this statement in the CBL 
2.0 setup guide at 
https://developer.couchbase.com/documentation/mobile/2.0/couchbase-lite/swift.html#story-h2-7
 :

> Sync Gateway 1.5 will automatically use the 1.x replication protocol when a 
> Couchbase Lite 1.x client connects through "http://localhost:4984/db"; and the 
> 2.0 replication protocol when a Couchbase Lite 2.0 client connects through 
> "ws://localhost:4984/db".

Is or is not SG 1.5 intended to support both 1.x and 2.0 clients? Or have I 
misunderstood what the doc is trying to say?

cheers,

-ben

-- 
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/23A75C03-ADF7-4D78-A52B-D0EA072B6097%40kashoo.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to