Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 53741 invoked from network); 13 Jan 2010 17:08:39 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 13 Jan 2010 17:08:39 -0000 Received: (qmail 23692 invoked by uid 500); 13 Jan 2010 17:08:38 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 23625 invoked by uid 500); 13 Jan 2010 17:08:37 -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 23615 invoked by uid 99); 13 Jan 2010 17:08:37 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Jan 2010 17:08:37 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of jchris@gmail.com designates 209.85.216.180 as permitted sender) Received: from [209.85.216.180] (HELO mail-px0-f180.google.com) (209.85.216.180) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Jan 2010 17:08:27 +0000 Received: by pxi10 with SMTP id 10so17506826pxi.13 for ; Wed, 13 Jan 2010 09:08:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to :content-type; bh=sQZyPEvUsfLo/0C1Kh6QKWd1sZoP/X3mitvTsXc7WSY=; b=I/ZTOfbpW/Yx35clDRoMSt4OIbjR308CMDC+u3WE3b+ekxabbFZww15d7YtHCrEGoZ aXtMqx0NDjeXDWVd+fpWiIw+Cdsy9tPwZBlnrQmHi8onIQLTDfhn0l5YR7DK81vQEDwY 89p8+t8mqBbZf7WEPdfxhE4A3Bd24w6qW6xUA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; b=gB/FQDOZfFkRzYthlIoT5mkMiw7xOQLX5Bx6cC5iSyWrAWH2AOkBoOMYdWA/4jvel/ C+8TkdHcN0B5cH5sA6dNdbZfwiTpd2hoxC89fpBlpHfFfWpGk1x97i91HzMQy1wijVxA 5TQTUDssA3Ot6Z1y2w+t8Y8o5SMbYvMYYL8A8= MIME-Version: 1.0 Sender: jchris@gmail.com Received: by 10.143.25.40 with SMTP id c40mr6600532wfj.265.1263402485831; Wed, 13 Jan 2010 09:08:05 -0800 (PST) In-Reply-To: <56a83cd01001130855o41d2897cgcb9a6ba7f0c2a9df@mail.gmail.com> References: <56a83cd01001130855o41d2897cgcb9a6ba7f0c2a9df@mail.gmail.com> Date: Wed, 13 Jan 2010 09:08:05 -0800 X-Google-Sender-Auth: ae2e7d4d4b71781f Message-ID: Subject: Re: GWT app stored and served from CouchDB? From: Chris Anderson To: user@couchdb.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org On Wed, Jan 13, 2010 at 8:55 AM, David Van Couvering wrote: > I'm looking at GWT as a way to ease my way from Java-land into > JavaScript-land. > > I really like the deployment model of CouchDB - no multiple tiers, no web > server to set up and configure, no hosting site to link up with (besides > cloudant). > > So, I am thinking I could push a GWT app (a bunch of HTML, JavaScript and > images) into CouchDB as attachments, and serve the app straight up from > CouchDB. > > Before I blithely go down this path, I'd like to ask those of you more > experienced in this world if there are any fundamental issues with doing > this (practical or philosophical). I've never used GWT but this sounds great in theory. Let us know how it works out. > > Thanks in advance, > > David > > -- > David W. Van Couvering > > http://www.linkedin.com/in/davidvc > http://davidvancouvering.blogspot.com > http://twitter.com/dcouvering > -- Chris Anderson http://jchrisa.net http://couch.io