Return-Path: Delivered-To: apmail-incubator-couchdb-user-archive@locus.apache.org Received: (qmail 72616 invoked from network); 12 Nov 2008 20:28:22 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 12 Nov 2008 20:28:22 -0000 Received: (qmail 3220 invoked by uid 500); 12 Nov 2008 20:28:28 -0000 Delivered-To: apmail-incubator-couchdb-user-archive@incubator.apache.org Received: (qmail 3191 invoked by uid 500); 12 Nov 2008 20:28:28 -0000 Mailing-List: contact couchdb-user-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: couchdb-user@incubator.apache.org Delivered-To: mailing list couchdb-user@incubator.apache.org Received: (qmail 3180 invoked by uid 99); 12 Nov 2008 20:28:28 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 12 Nov 2008 12:28:28 -0800 X-ASF-Spam-Status: No, hits=3.2 required=10.0 tests=HTML_MESSAGE,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [74.125.44.157] (HELO yx-out-1718.google.com) (74.125.44.157) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 12 Nov 2008 20:27:10 +0000 Received: by yx-out-1718.google.com with SMTP id 36so269501yxh.0 for ; Wed, 12 Nov 2008 12:27:43 -0800 (PST) Received: by 10.90.87.7 with SMTP id k7mr8546667agb.85.1226521663104; Wed, 12 Nov 2008 12:27:43 -0800 (PST) Received: by 10.90.90.17 with HTTP; Wed, 12 Nov 2008 12:27:43 -0800 (PST) Message-ID: <64a10fff0811121227n120697dbk3805586357fbc9c0@mail.gmail.com> Date: Wed, 12 Nov 2008 15:27:43 -0500 From: "Dean Landolt" To: couchdb-user@incubator.apache.org Subject: Re: Seeking advice on using couchdb for rewritting a project. In-Reply-To: <4650D767-4AD5-440B-8493-94AC85631F8C@prima.de> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_16967_4939629.1226521663079" References: <4919C8A7.8030409@gmail.com> <2966DD15-EBB2-47E8-8F17-6A74888B7829@gmail.com> <64a10fff0811121126o22fe1bcbtadd09f1252fd24a@mail.gmail.com> <4650D767-4AD5-440B-8493-94AC85631F8C@prima.de> X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_16967_4939629.1226521663079 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline On Wed, Nov 12, 2008 at 2:34 PM, Jan Lehnardt wrote: > > > On 12.11.2008, at 19:26, "Dean Landolt" wrote: > > On Wed, Nov 12, 2008 at 12:55 PM, Paul Davis > >wrote: >> >> On Wed, Nov 12, 2008 at 12:44 PM, tasman wrote: >>> >>>> >>>> On Nov 11, 2008, at 8:02 PM, Burobjorn wrote: >>>> >>>> Hi everybody, >>>>> >>>>> My name is Bjorn Wijers and I recently started to play with couchdb. >>>>> It's a very interesting project and I would like to use it to rewrite >>>>> an >>>>> older project called Simuze[1], but I wonder if couchdb would be the >>>>> right tool for the job. Perhaps some of you can help me out in >>>>> understanding the pro's and con's of using couchdb for this? >>>>> >>>>> Simuze is musicplatform (website) for musicians and music fans by >>>>> non-profit Stichting (=Foundation) Open Media. Artists can upload their >>>>> music under a Creative Commons license of their choosing and music >>>>> lovers can download these songs from the site. It was built quite some >>>>> time ago in PHP and MySQL. >>>>> >>>>> The basics in this application are: >>>>> >>>>> - users >>>>> >>>>> - profiles (might be multiple per user, since a user may have more than >>>>> one artist persona) >>>>> >>>>> - media files (images and audio for now) >>>>> >>>>> - media collections (such as a playlist or album) >>>>> >>>>> - ratings (every media file or collection) >>>>> >>>>> - tags (everything) >>>>> >>>>> Our objective is to rewrite Simuze in such a way that we can distribute >>>>> it as an 'easy' to install webapplication under a free/open-source >>>>> license (Affero GPL). We would like to connect all the different Simuze >>>>> installs (replication would be very helpful for this, I guess) and >>>>> create a distributed free (as in CC licensed and PD) music web. Think >>>>> of >>>>> it as a non-suck MySpace built by musicians ;) >>>>> >>>>> Some questions that I have are: >>>>> >>>>> 1) Would this type of application be suitable for couchdb or is this >>>>> better suited by using a RDBMS? >>>>> >>>> >>>> It depends more on "queries", that you will need. >>>> >>>> >>>>> 2) Could we use the attachment feature for adding media files (FLAC or >>>>> WAV or AIFF files roughly 50 MB per file) to couchdb? Or is this not >>>>> advisable given the size of the files? The reasoning behind this is >>>>> that >>>>> by using replication we can easily backup the whole system or setup an >>>>> another node of it. Therefor having everything in one place seems like >>>>> a >>>>> good idea? >>>>> >>>> >>>> Saving big attachments into CouchDB sounds like not good idea, i think. >>>> AFAIK your binary attachments store into CouchDB in base64 encoding, so >>>> their size increase. And replication mechanism isn't too fast yet. >>>> >>>> Please correct me, if it's wrong. >>>> >>>> >>> This used to be correct. Attachments no longer have to be base64 >>> encoded when using the standalone attachments API. >>> >> >> >> One thing I've wondered about was streaming? At some point I want to dump >> in >> my mp3 collection and write a simple _external app with a flash music >> player >> that could play songs on the fly. My guess is it would work fine with >> chunked responses, but what about jumping ahead past a buffered point? >> > > Jumping doesn't work yet. Can you open a JIRA feature request for the > skipping? I might give it a shot. I can open a JIRA for an arbitrary seek, which may be universally useful, but it probably wouldn't work for things like variable bit rate mp3s, and I doubt it would work for serving video (something couch is otherwise pretty well suited for). I remember reading that for certain container formats of video this is possible with a special index in the beginning of the file. Of course, all of this would be way out of scope for couch to know about -- it would probably make a great plugin though. ------=_Part_16967_4939629.1226521663079--