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 688EE9B8C for ; Fri, 16 Mar 2012 19:43:19 +0000 (UTC) Received: (qmail 34340 invoked by uid 500); 16 Mar 2012 19:43:18 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 34180 invoked by uid 500); 16 Mar 2012 19:43:17 -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 34169 invoked by uid 99); 16 Mar 2012 19:43:17 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 16 Mar 2012 19:43:17 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [209.85.210.52] (HELO mail-pz0-f52.google.com) (209.85.210.52) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 16 Mar 2012 19:43:11 +0000 Received: by dadp12 with SMTP id p12so7277315dad.11 for ; Fri, 16 Mar 2012 12:42:49 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:x-gm-message-state; bh=+IyHHx8lEblUhhtbqNI+LSaTHrJNI/9wvdI+CoomTOs=; b=kvWSo6ObxYOqcHLO5T/rW8oTTwt5/hN9hJfTEDjmgq7ShBDvpyPKxgWHF2HjasTTHi hjdOMrgaCocVDBBoo0gPhlGrlA7juU/ADbOjFuGuPiXNn5dsHrJgjo5jpR9ETYYXuZR2 G8SYSJzsw7OQMDCNfMy6LMjaBIuVvOoInLwxTXOJ3FyxkpgrJE/7PObtamKMHK28QJSq BP/jtYoDULInbfzhuCugDDjvvDWBuASLvrWsNUUbVgcQfwd3GSURR/FXQ9Ek1nZ+PwCW rgZ5GGPbAdXewlMzw31fpfqVXgVoVqVhE3xSb+6lo2HHnnZUNdo1hTbcEVGqwECUtnqj s4wg== MIME-Version: 1.0 Received: by 10.68.204.131 with SMTP id ky3mr435319pbc.69.1331926969091; Fri, 16 Mar 2012 12:42:49 -0700 (PDT) Received: by 10.68.29.5 with HTTP; Fri, 16 Mar 2012 12:42:48 -0700 (PDT) In-Reply-To: References: Date: Fri, 16 Mar 2012 12:42:48 -0700 Message-ID: Subject: Re: Mobile sync use cases From: Jay Zamboni To: user@couchdb.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQmvIKkCqkWS1IwexV5gKUl5vo+aV4AScBA52wRUgW9yMU6vKyKcf9MxKPjVq5fub5xYkzig X-Virus-Checked: Checked by ClamAV on apache.org Hello Chris, thanks for asking. > Are you interested in a solution that bridges big data on the server, > with user-level subsets on the phone? Yes > Is there a collaborative aspect to your data? Will disconnected users > potentially be working on the same data and generating conflicting > edits? Yes The big data with user-level subsets is our typical usage, but our users subsets will often overlap. So while our users can only see some data, it does not mean they are the only ones who can see and change that data. Our concerns with replication in this situation are mostly security. Either a record level security or a way to secure server replication so that it requires the use of a filter and have the filter able to perform a security check, would be great for us. Jay On Fri, Mar 16, 2012 at 12:02 PM, Chris Anderson wrote: > Hello CouchDB users, > > I know some of you are interested in the potential of CouchDB style > sync, to bring offline data access to users on mobile devices. > > Couchbase has invested a lot of time into building CouchDB compatible > implementations for mobile devices. [1] > > We are getting to the point in the product development cycle where we > need to make some hard decisions, about which use cases to prioritize, > and which cases are better left to fend for themselves. I have a few > questions which will help us know what the bulk of the users are > thinking of doing on mobile platforms. > > If you prefer to reply privately, feel free to email me at jchris at > apache.org or jchris at couchbase.com - thanks in advance! > > Are you interested in a solution that bridges big data on the server, > with user-level subsets on the phone? Eg the data in the cloud would > be in a repository that contains all of the user data, with queries to > split out the data for a given user. (Think filtered replication on > steroids.) > > Or is it more about keeping a single user's data up to date across > their devices? This is more like Apple iCloud or Dropbox, and would > have less need for a centralized consolidated database and advanced > query based sync filtering. > > Is there a collaborative aspect to your data? Will disconnected users > potentially be working on the same data and generating conflicting > edits? > > Cheers! > Chris > > [1] http://www.couchbase.com/wiki/display/couchbase/Couchbase+Mobile+Syncpoint > > -- > Chris Anderson > http://jchrisa.net > http://couchbase.com