Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 48643 invoked from network); 13 Jan 2010 16:56:25 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 13 Jan 2010 16:56:25 -0000 Received: (qmail 81543 invoked by uid 500); 13 Jan 2010 16:56:24 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 81493 invoked by uid 500); 13 Jan 2010 16:56:24 -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 81483 invoked by uid 99); 13 Jan 2010 16:56:24 -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 16:56:24 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of david.vancouvering@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 16:56:12 +0000 Received: by pxi10 with SMTP id 10so17496694pxi.13 for ; Wed, 13 Jan 2010 08:55:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=ORwbTAl0JcjzS/vAMEWG/v1fZeMLsYpz+y7AAQukiNU=; b=Ph6TfWiopIFOFJ59U1WApHcImXJeFBFqigbTKX6djnnPimUo55V+nfoWV0ib0Sq5rR Hos8/N2ncMMyy6HOBiN92NoeK8Dt3ZSdofYGidK8aQHyURLjN5Bs5T+1iTJESEnXXhap FzDIjFftj2JLGXmFUQZ2UAXfHpH25qqDQpDwo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; b=jWjJNoAaeKBCt2Xa8ETLJHdnpnjN7dOnuUrxFCZ4pHh0HKIoN3H4FrCRw2kaarZ9cb 6Qg3fevXoX2VATalr7PXLpWxv+wRMFMtJFkHKQQzuwp1yopjAdsPGbn2N80vEsVIaU7p jmL2z13oBSf8nbVDGwXXYcL+Xhpf5ea016i3c= MIME-Version: 1.0 Sender: david.vancouvering@gmail.com Received: by 10.141.88.6 with SMTP id q6mr1309431rvl.182.1263401751415; Wed, 13 Jan 2010 08:55:51 -0800 (PST) Date: Wed, 13 Jan 2010 08:55:51 -0800 X-Google-Sender-Auth: e35b38adc03806a5 Message-ID: <56a83cd01001130855o41d2897cgcb9a6ba7f0c2a9df@mail.gmail.com> Subject: GWT app stored and served from CouchDB? From: David Van Couvering To: user Content-Type: multipart/alternative; boundary=000e0cd13a709a0c6c047d0ea470 X-Virus-Checked: Checked by ClamAV on apache.org --000e0cd13a709a0c6c047d0ea470 Content-Type: text/plain; charset=ISO-8859-1 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). Thanks in advance, David -- David W. Van Couvering http://www.linkedin.com/in/davidvc http://davidvancouvering.blogspot.com http://twitter.com/dcouvering --000e0cd13a709a0c6c047d0ea470--