> On Aug 13, 2014, at 4:36 PM, Nick Pavlica <[email protected]> wrote: > > 1. All new applications that use offline/online syncing should use the Sync > Gateway Rest API exclusively to avoid the duplicate work created by shadowing > a bucket?
It depends. In most cases, yes. But if you explicitly want to use the Couchbase Server APIs as well (maybe you're an expert at it, or you want to use a library that uses it) you'll need bucket shadowing. > 1(A). Will the native drivers be updated to implement the necessary > components for syncing, allowing native access to the data without the need > of the Sync Gateway? I'm not sure what you mean by this? Do you mean extending the Couchbase SDKs to add support for calling the Sync Gateway REST API? You'd have to ask the SDK team about that. (But there are existing libraries for the same languages for communicating with CouchDB, which uses the same REST API as the Sync Gateway, so you can use those.) > 1(B). Alternatively, will Couchbase server be modified so that it handles > the syncing components without requiring the Sync Gateway? It's unclear. That depends on architectural decisions that haven't been made yet. > 2. The Sync Gateway doesn't currently have CORS support. Is this support > planned, if so, what is the timeline? There's an issue for it in Github; I don't remember whether it's been assigned a milestone. (Or possibly it's been fixed since 1.0.1?) > 2(A). Instead of using the Sync Gateway directly from browser based > apps(Angualrjs,ETC.) should you use a server based "Web Framework" that > utilizes the Sync Gateway APIs for traditional Browser facing UI's? Yes, for now. The Sync Gateway API doesn't yet expose a way to query views, and that really limits what you can do with it directly. > 3. Does the use of the Sync Gateway limit the full functionality of > Couchbase Server? Only in that you shouldn't use Couchbase Server APIs to write to the gateway's bucket directly. > 4. Can PouchDB, and Apache CouchDB be used safely with the Sync Gateway? Yes, for the most part. There are a few compatibility issues (see Github for details.) The one that I remember is that PouchDB doesn't yet support MIME multipart format for downloading docs with attachments, but Sync Gateway doesn't support the older all-JSON format. > 5. When using the Sync Gateway, are there any special considerations to make > when modeling your documents? As opposed to using what? It's going to be mostly the same as using CouchDB or PouchDB, but of course very different from a relational db. The differences from *ouchDB would be in how to deal with channel assignment, i.e. using properties to denote what channel the document should be in or what channels are otherwise associated with it. —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]. To view this discussion on the web visit https://groups.google.com/d/msgid/mobile-couchbase/128ECEFA-195A-492D-8780-3C791ADAA79E%40couchbase.com. For more options, visit https://groups.google.com/d/optout.
