From user-return-15993-apmail-couchdb-user-archive=couchdb.apache.org@couchdb.apache.org Tue Apr 26 10:25:08 2011
Return-Path:
X-Original-To: apmail-couchdb-user-archive@www.apache.org
Delivered-To: apmail-couchdb-user-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
by minotaur.apache.org (Postfix) with SMTP id 915071B68
for ; Tue, 26 Apr 2011 10:25:08 +0000 (UTC)
Received: (qmail 70919 invoked by uid 500); 26 Apr 2011 10:25:07 -0000
Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org
Received: (qmail 70873 invoked by uid 500); 26 Apr 2011 10:25:06 -0000
Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
List-Help:
List-Unsubscribe:
List-Post:
List-Id:
Reply-To: user@couchdb.apache.org
Delivered-To: mailing list user@couchdb.apache.org
Received: (qmail 70865 invoked by uid 99); 26 Apr 2011 10:25:06 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 26 Apr 2011 10:25:06 +0000
X-ASF-Spam-Status: No, hits=1.5 required=5.0
tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,RFC_ABUSE_POST,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of philipp.forsthuber@googlemail.com designates 209.85.160.180 as permitted sender)
Received: from [209.85.160.180] (HELO mail-gy0-f180.google.com) (209.85.160.180)
by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 26 Apr 2011 10:25:01 +0000
Received: by gyf2 with SMTP id 2so255799gyf.11
for ; Tue, 26 Apr 2011 03:24:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=googlemail.com; s=gamma;
h=domainkey-signature:mime-version:in-reply-to:references:from:date
:message-id:subject:to:content-type;
bh=NT1CqfnitmVA8j/ccQ6eYWWQzOgN+w0jPc0kvpS/CP0=;
b=tNDpHomrlzI0pUnH/5acbcSe/acNzKEJAEHjChIcyu7hcODidm+5Ao3fHAGp4lfAsF
6J75FWN1suPDfMLgoCvKpjiqmGJ0j5I9JqUeG6ieYM4LYpxc0oB0kGkYEntunYFZmYcG
8cznW+oIAJpw8l3hZWbuCq/VbqaRLdv56+G8I=
DomainKey-Signature: a=rsa-sha1; c=nofws;
d=googlemail.com; s=gamma;
h=mime-version:in-reply-to:references:from:date:message-id:subject:to
:content-type;
b=Y//kT15Z40ULmj1xv0WahA/wqXVqxYFUP8WtK8KPKPbwdDDDzZcjc8xuUZFwitqRqe
DKzgfutcaZ8ZzrnWHaTFlt18EEr4XB+cxnASZeenYc3FnLWIv0NN1de9T0ycWfUf5fiQ
O2qvljuLNJSMyPNQUzpvxiiBoPLIqs4BTf+e4=
Received: by 10.151.19.34 with SMTP id w34mr542794ybi.140.1303813479117; Tue,
26 Apr 2011 03:24:39 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.150.226.5 with HTTP; Tue, 26 Apr 2011 03:23:59 -0700 (PDT)
In-Reply-To:
References: <4DB06591.4060600@gmail.com>
From: Philipp Forsthuber
Date: Tue, 26 Apr 2011 12:23:59 +0200
Message-ID:
Subject: Re: Help needed: is couchDB a good fit for my app?
To: user@couchdb.apache.org
Content-Type: multipart/alternative; boundary=000e0cdf0f9e46b4fb04a1cfbb20
--000e0cdf0f9e46b4fb04a1cfbb20
Content-Type: text/plain; charset=ISO-8859-1
Hello Joel,
First of all, sorry for me taking so long to answer, I have been sick over
the past few days, and only now recovering.
I am afraid you misunderstood me. What we implemented with the RESTful
webservice only let the client on the smartphone register a user and
generate the needed databases, so that we could use a secure connection and
need not submit the password as plaintext to couchDB. The replication then
is done via filters that are defined to only synch those documents back to
the user DB on the server that adhere to a specific scheme (Bulletpoint 5 in
my original message).
The reason we did it this way: If we do not use a master database, then
every user has access to all the data that is stored on the server. If we do
it like this, we delegate the task of managing the data that is to be
replicated to a trusted third party, aka the concierge system at the master
database.
I am sorry if I sounded like I had some more sophisticated solutions,
perhaps even as a plugin to couch, but this is the simplest and most secure
way we could devise such a system.
@Jeoren: You are absolutely right, filtered replication is is the easiest
way to do it, but keep in mind that a three-tiered database structure is a
must if you want to synch data between multiple users, because of the
permission system in couch.
I hope to have cleared this up a little,
regards,
Philipp
2011/4/25 Jeroen van Dijk
> >
> >
> >
> > @Philipp :
> >
> > Could you point us to some more detailed references? Maybe to the copy of
> > (an extract of) your thesis? Or even to an implementation of your
> > webservices for per-document authorization?
> >
> >
> Having a similar use case, I would also be very interested to read more
> about this approach. So far I don't understand why this approach is needed
> when it seems one could also use:
> http://wiki.apache.org/couchdb/Replication#Filtered_Replication directly.
> However, I have no practical experience with this so I would be happy to
> hear why that is not feasible.
>
> Thanks,
> Jeroen
>
--000e0cdf0f9e46b4fb04a1cfbb20--