Am 18.01.2014 um 09:51 schrieb Jens Alfke <[email protected]>:
>
> On Jan 17, 2014, at 11:52 PM, Francisco Garcia <[email protected]>
> wrote:
>
>> Now everything makes sense. When testing the gateway installation, the whole
>> time my mind was set to "Gateway running, look for the Gateway API" when
>> actually, the API was inside the CBL documentation. I ignored this thinking
>> that I should not deal with HTTP REST calls inside CBL
>
> You realize it's just the CouchDB API, right? (Or rather, large subsets of
> it, plus extensions.)
I did notice the similarities, and that is the reason I decided to explore the
gateway using REST calls before looking at the CBL examples
However regarding the concern I mentioned in my previous reply (regarding Sync
Gateway SDK and possible corruption using CouchBase SDK)
If the intention is to keep as much compatibility as possible with the CouchDB
API. There is something that could 'potentially' make the gateway compatible
with many third party libraries. For example, this is how I add a document to
CouchDB with Ruby:
db = CouchRest.database('http://localhost:4985/rubase/')
db.save_doc({key:'joe'})
However with the Gateway the above call fails with:
RestClient::MovedPermanently: 301 Moved Permanently
I believe it is only because the gateway redirects instead of accepting urls
with/without final '/'
Although each library implementation is different. It looks like accepting
instead redirecting could potentially ease the compatibility with CouchDB
clients in many languages.... but I am not sure how much compatibility is
intended, and if we should just blame the implementation I am using now
--
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/4D14E49F-AF16-48AB-A701-1B7DE6827544%40francisco-garcia.net.
For more options, visit https://groups.google.com/groups/opt_out.
