On Mar 5, 2014, at 8:04 AM, Sebastien Flaesch <[email protected]> wrote:
> I don't think we should have wrappers for all CBLite native APIs, as classes > in our language. > Our solution cannot be platform specific, and I suspect that CBLite Native > APIs for iOS and Android are a bit different... The Couchbase Lite bridges to Titanium and MonoTouch use wrappers to the native APIs. The Objective-C and Java APIs are conceptually the same, though there are differences because they're in different languages. > Why would the CBLite Native APIs be faster than the REST API? > I thought the native APIs are built on top of the REST API... No, the other way around. It's a native implementation with native APIs, and there's an adapter on top of that (the CouchbaseLiteListener framework, on iOS) that adds the HTTP handlers. We had an earlier version where the native APIs were wrappers around REST calls, but it was significantly slower and required more code. --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/0FE31F29-56D0-4661-8FAB-C779A66AFFEC%40couchbase.com. For more options, visit https://groups.google.com/groups/opt_out.
