Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 15719 invoked from network); 20 Aug 2010 01:04:17 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 20 Aug 2010 01:04:17 -0000 Received: (qmail 37076 invoked by uid 500); 20 Aug 2010 01:04:16 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 36980 invoked by uid 500); 20 Aug 2010 01:04:16 -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 36972 invoked by uid 99); 20 Aug 2010 01:04:16 -0000 Received: from Unknown (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 20 Aug 2010 01:04:16 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of Whimsica@aol.com designates 205.188.91.97 as permitted sender) Received: from [205.188.91.97] (HELO imr-db03.mx.aol.com) (205.188.91.97) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 20 Aug 2010 01:03:50 +0000 Received: from imo-ma01.mx.aol.com (imo-ma01.mx.aol.com [64.12.78.136]) by imr-db03.mx.aol.com (8.14.1/8.14.1) with ESMTP id o7K13PhS027370 for ; Thu, 19 Aug 2010 21:03:25 -0400 Received: from Whimsica@aol.com by imo-ma01.mx.aol.com (mail_out_v42.9.) id o.efb.3ec0059 (45300) for ; Thu, 19 Aug 2010 21:03:20 -0400 (EDT) Received: from smtprly-db02.mx.aol.com (smtprly-db02.mx.aol.com [205.188.249.153]) by cia-mc04.mx.aol.com (v129.4) with ESMTP id MAILCIAMC044-5c364c6dd4531c5; Thu, 19 Aug 2010 21:03:20 -0400 Received: from Webmail-m112 (webmail-m112.sim.aol.com [64.12.232.220]) by smtprly-db02.mx.aol.com (v129.4) with ESMTP id MAILSMTPRLYDB024-5c364c6dd4531c5; Thu, 19 Aug 2010 21:03:15 -0400 References: <8CD0E06BDB49329-4B6C-2E19@Webmail-m112.sysops.aol.com> To: user@couchdb.apache.org Subject: Re: reverse proxy discouraged? Date: Thu, 19 Aug 2010 21:03:15 -0400 X-AOL-IP: 75.30.177.43 In-Reply-To: X-MB-Message-Source: WebUI MIME-Version: 1.0 From: whimsica@aol.com X-MB-Message-Type: User Content-Type: multipart/alternative; boundary="--------MB_8CD0E1A9AA5CBF8_4B6C_70B8_Webmail-m112.sysops.aol.com" X-Mailer: AOL Webmail 32447-STANDARD Received: from 75.30.177.43 by Webmail-m112.sysops.aol.com (64.12.232.220) with HTTP (WebMailUI); Thu, 19 Aug 2010 21:03:15 -0400 Message-Id: <8CD0E1A9A9C4674-4B6C-4AF4@Webmail-m112.sysops.aol.com> X-AOL-SENDER: Whimsica@aol.com X-Virus-Checked: Checked by ClamAV on apache.org X-Old-Spam-Flag: NO ----------MB_8CD0E1A9AA5CBF8_4B6C_70B8_Webmail-m112.sysops.aol.com Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="us-ascii" What about these scenarios: 1. I have a web 2.0 GUI based application where a user can create some con= tent by pushing buttons and writing snippets of code -- the end result is= stored as text -- and then saved to the database. 2. I want the user to be able to list their files, edit them, then resave= them -- all from the web 2.0 interface. or 1. I have a web 2.0 application where users input the vitamins levels the= y take vs their symptom levels for each day. Each day they can input their own symptom descriptions and values like 1 to 10. 2. When prompted, the system grabs all their data and runs statistics on= it in javascript. In each case I want to do authentication -- like login/session/signup. That kind of thing. The web 2.0 GUI interfaces for both these projects involve 1000's of lines of javascript from different libraries, and multiple graph= ic image sets for the GUI, all of which are changing all the time during the development process.=20 How is couchdb used in these scenarios. Right now I'm trying to get it wor= king with couch.js but running into the cross domain problem. I can't sen= d anything from an html page into the :5984 port. Thanks, Dan =20 =20 =20 -----Original Message----- From: Randall Leeds To: user@couchdb.apache.org Sent: Thu, Aug 19, 2010 4:42 pm Subject: Re: reverse proxy discouraged? I think for your use case a reverse proxy is fine, especially if the 'web2.0' content is a server itself running python/ruby/perl/java/erlang/scala/node/insert/favorite/middleware/here At which point you likely don't even need to expose couch to the outside at all. Just put it in your private network and access it from your application server. Exposing couch directly to the world via a reverse proxy is probably only a good plan if you need to co-host a public couch with other apps or static files behind different virtual hosts or if you want to do complicated authentication in front of your couch that couchdb can't do itself. -Randall On Thu, Aug 19, 2010 at 15:41, wrote: > Is using a reverse proxy to serve up html and couchdb from the same doma= in and=20 port problematic? > Someone told me that it is highly discouraged > > and that html pages should be served from couchdb. > But on a site that is web 2.0 and has a complicated GUI there would need= to be=20 100's of attachments that would be necessary to correctly > serve up a page as an attachment to a document. > > This sounds unreasonable for development where 100's of changes are made= per=20 day. > > The reverse proxy method seems feasible but why would it be discouraged? > > Thanks, > > Dan > > > > > > > > =20 ----------MB_8CD0E1A9AA5CBF8_4B6C_70B8_Webmail-m112.sysops.aol.com--