Thanks for the material and tips Jens :)

BR,
Thiago


On Thursday, February 4, 2016 at 5:45:56 PM UTC+1, Jens Alfke wrote:
>
>
> On Feb 3, 2016, at 6:24 PM, Thiago Alencar <[email protected] 
> <javascript:>> wrote:
>
> I'll be presenting on the next Cocoaheads event here in Berlin about 
> Couchbase. There is already more than 100 people confirmed.
>
>
> That’s great! Thanks a lot for doing this. It’s well timed, since we just 
> released 
> Couchbase Mobile 1.2 
> <http://blog.couchbase.com/2016/january/announcing-couchbase-mobile-1.2> 
> today 
> :-D
>
> If any of you know of a feature worth mentioning, or have some 
> supplemental material, I'd be grateful to have it :)
>
>
> I’ll post in a minute about the new features in the 1.2 components.
> Also, here are the slides 
> <https://speakerdeck.com/snej/couchbase-mobile-101> of my “Couchbase 
> Mobile 101” presentation from last May.
>
> Maybe I'm a bit outdated, quick question: how's the status of shadow 
> buckets? Is this no longer the recommended way of interacting with the data 
> from the backend side, or should we be using purely the sync gateway's REST 
> API?
>
>
> The REST API is preferred because it’s cleaner and more supportable going 
> forward. But bucket shadowing is still supported, and can be necessary in 
> some cases where you’ve got existing Couchbase buckets managed by an app 
> server that you want to expose to mobile clients. 
>
> We’re working on integrating Sync Gateway more deeply into the Couchbase 
> server itself, so mobile client and app servers can share a single bucket, 
> but that’s still a ways out.
>
> —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/c0cf5f6b-97b1-47c1-904f-754d30582305%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to