On 06/03/2014 06:51 PM, Jens Alfke wrote:
On Jun 2, 2014, at 2:08 PM, Volker Mische <[email protected]
<mailto:[email protected]>> wrote:
I just got a question whether it is possible on Android to have a
central Couchbase Lite instance that holds the data and then
independent apps that access it. For example with using the Android
LiteServ (having access through HTTP would be good enough).
What's the advantage of doing it this way, as opposed to each app using
its own embedded CBL? (That's not a rhetorical question; I know there
can be advantages for certain use cases. For example, to share a very
large database without duplication, or to let apps operate on shared data.)
The idea is to have a central data provider where each user can download
his specific data. It may be worth several GBs (though I don't know if
that's really feasible with CBL). Then third parties should be able to
build apps on top of it.
CBL isn't intended to be a server and I'm a little bit wary of it being
used as one, mostly for security reasons. I don't know if the listener
implementation on Android supports passwords, for example. And it needs
to be careful to avoid binding to network interfaces other than loopback
(127.0.0.1) or it'll be reachable from other devices on the network,
which greatly increases the attack surface.
I'm also concerned about the security, but I would expect the central
CBL that holds the data to be more of a read only thing. It will sync to
get updates, but I don't expect the apps to change anything of it.
Cheers,
Volker
--
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/538F1F41.2020304%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
