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 2B460D2F1 for ; Wed, 6 Mar 2013 17:01:31 +0000 (UTC) Received: (qmail 10207 invoked by uid 500); 6 Mar 2013 17:01:29 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 10157 invoked by uid 500); 6 Mar 2013 17:01:29 -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 10138 invoked by uid 99); 6 Mar 2013 17:01:28 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Mar 2013 17:01:28 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [209.85.220.180] (HELO mail-vc0-f180.google.com) (209.85.220.180) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Mar 2013 17:01:24 +0000 Received: by mail-vc0-f180.google.com with SMTP id fo13so4913152vcb.39 for ; Wed, 06 Mar 2013 09:01:01 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type:x-gm-message-state; bh=k2FVQxeDts3+yxnXVIdppmUKNZYk/JjipcYr4gVuV64=; b=XQRIE2BSCnziTyaPUNU3XMfgAL8fwsFldmKymZhHcs81kkkYrMn/BB42pwnfJpqfFC PL7BfKZ2eZudUbVP5pmBHzDDsWdC2w4ovt+4Voe2I0ocduAZJRtoynw9dt1sPEH/OF1t 7Q6NmTjOck7ayPGNGPhDTUELTH0F5Vp0qMpkHyzZ+boJC9gtRC+yqnzvsAcR/C0llzoz q24sbGyylKJQKI1EcfGCMEuNdQKCR5FXZRZz1a86ouLbYszjPKsio4lDGQlQKQu8y6P8 zx8XjdNtv2+P9Xv2akNPVkkYkJAhPg6rtcevwkZXbXcIqpPxRnojJXwz9Bb7Z65fZhKc EODg== MIME-Version: 1.0 X-Received: by 10.220.39.69 with SMTP id f5mr11667046vce.45.1362589261510; Wed, 06 Mar 2013 09:01:01 -0800 (PST) Received: by 10.220.34.197 with HTTP; Wed, 6 Mar 2013 09:01:01 -0800 (PST) In-Reply-To: References: Date: Wed, 6 Mar 2013 18:01:01 +0100 Message-ID: Subject: Re: Curiosity how you use CouchDB in your web env. From: =?UTF-8?Q?Johannes_J=C3=B6rg_Schmidt?= To: user@couchdb.apache.org Content-Type: multipart/alternative; boundary=bcaec54eebbae8809504d74488b8 X-Gm-Message-State: ALoCoQlz6IMK7ACAt3y4LqiOW7k7z/fgT2yaJlWLq8c5Tnh3XtW3SnIHpWlRqiuiz2JU/vU11+h9 X-Virus-Checked: Checked by ClamAV on apache.org --bcaec54eebbae8809504d74488b8 Content-Type: text/plain; charset=UTF-8 I love to reduce the server stack and use nothing more than CouchDB. I often render HTML via show and list functions (mostly list functions) and after the first hit I let the client take over. 2013/3/6 Dan Santner > I use couchdb as a restful doc persistence. I don't use CouchApp. > On Mar 6, 2013, at 10:45 AM, Mark Hahn wrote: > > > I have a node app that does all html serving and my app talks directly to > > couch via 127.0.0.1. I think this is the most common setup. > > > > > > On Wed, Mar 6, 2013 at 8:21 AM, TAE JIN KIM > wrote: > > > >> There are couple of ways that CouchDB can be used in web development. > >> > >> You could deploy your html as attachment in _design in your couch db..so > >> actually couchdb could serve your html.... > >> You could create a kind of proxy middle layer so that this can > communicate > >> between your presentation layer and your CouchDB due to cross-domain > issue > >> of Ajax.. > >> There might be some different way as well.... > >> > >> There is no obvious right answer approach here I guess, but just out of > >> curiosity, would like to hear > >> how CouchDB is being used in your web environment.... > >> if you had all of experience as far as deployment is concerned, that > would > >> be great if you could share for each pros/cons as well... > >> > >> Thanks in advance. > >> > >> > >> > >> > > --bcaec54eebbae8809504d74488b8--