Thanks again for the prompt response. - So the CouchbaseLiteListener internally creates a HTTP server on the device itself and all the REST API calls are submitted to this local HTTP server on the device itself. The actual magic of inserting/updating data happens inside the CouchbaseLiteListener .
- Why CouchBaseLite chose this round about way of invoking the plugin ? Wouldn't it have been easier if they would have provided a one to one mapping of the JS APIs in the pluging itself. - We checked the URL that gets used when the plugin is initialized . It is something like this http://lite.couch. How does this URL maps to local host ? On Wednesday, May 20, 2015 at 9:15:23 PM UTC+5:30, Jens Alfke wrote: > > On May 20, 2015, at 8:36 AM, [email protected] <javascript:> wrote: > > - JS Wrappers internally call Rest APIs which internally call Cardova > Plugin which uses the CouchbaseLite and CouchbaseLiteListener frameworks to > update data in SQLLite storage. Is this understanding correct ? > > > The plugin isn’t involved. The REST API goes directly to the > CouchbaseLiteListener’s handlers. > (All the plugin does is initialize Couchbase Lite. That’s why there’s so > little code in it.) > > - So in a Cardova application for every REST API invoked an equivalent > plugin code that gets called. If that is the case how do the app > differentiate when it needs to use the REST API to call the server or it > needs to divert the REST API calls to the Cardova Plugin . > > > The app never needs to talk directly to a server. It only talks to > Couchbase Lite. > > —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/ffaeb9c6-f26b-4a58-90e7-54f1da3e3140%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
