From user-return-5773-apmail-couchdb-user-archive=couchdb.apache.org@couchdb.apache.org Sun Aug 02 09:56:15 2009 Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 7119 invoked from network); 2 Aug 2009 09:56:15 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 2 Aug 2009 09:56:15 -0000 Received: (qmail 14071 invoked by uid 500); 2 Aug 2009 09:56:17 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 13988 invoked by uid 500); 2 Aug 2009 09:56:17 -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 13978 invoked by uid 99); 2 Aug 2009 09:56:17 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 02 Aug 2009 09:56:17 +0000 X-ASF-Spam-Status: No, hits=-1.0 required=10.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [66.111.4.25] (HELO out1.smtp.messagingengine.com) (66.111.4.25) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 02 Aug 2009 09:56:07 +0000 Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id 52E783BC134; Sun, 2 Aug 2009 05:55:46 -0400 (EDT) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by compute1.internal (MEProxy); Sun, 02 Aug 2009 05:55:46 -0400 X-Sasl-enc: WxjznYZvCGp4VUsYwAjEMY9jSfrdA2F9rFghglSgfFmk 1249206947 Received: from NitinBorwankarsComputer.local (c-71-202-180-50.hsd1.ca.comcast.net [71.202.180.50]) by mail.messagingengine.com (Postfix) with ESMTPA id 20FDE1C2B for ; Sun, 2 Aug 2009 05:55:47 -0400 (EDT) Message-ID: <4A75629E.8030901@borwankar.com> Date: Sun, 02 Aug 2009 02:55:42 -0700 From: Nitin Borwankar User-Agent: Thunderbird 2.0.0.22 (Macintosh/20090605) MIME-Version: 1.0 To: user@couchdb.apache.org Subject: Re: couch returning text/plain for responses - is this correct ? References: <4A7543F2.7030804@borwankar.com> <4A754931.70207@borwankar.com> <4A754B2A.60508@borwankar.com> <603F7B11-5D1C-4132-ABA0-30368AF5654F@gmail.com> <4A75540A.6050306@borwankar.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Paul Joseph Davis wrote: > > > > > On Aug 2, 2009, at 4:53 AM, Nitin Borwankar wrote: > >> Paul Joseph Davis wrote: >>> >>> >>> [...] >>>> >>>> >>> >>> Well, for jquery with couchdb I'd just point people at >>> jquery.couch.js for most answers. Though that could be me being >>> lazy. Feel free to add where you think is appropriate. The wiki is a >>> wiki after all. :) >>> >> >> For people like me coming from a very rudimentary UI experience level >> - a slower descent into the hel.. er I mean depths of jquery is >> preferred :-). >> I love jQuery but the more advanced syntax is a steep curve for a few >> days. >> I tried the jquery.couch.js approach first - but just the number of >> concepts to be assimilated before I could get one thing done were too >> much. >> The functional syntax takes some getting used to and just trying to >> figure what scope I am in at each line of the code is mind twisting. >> >> Most jQuery tutorials are focused on DOM manipulation whereas my >> first interest is/was making calls to couch and getting json back - >> this usually comes towards th end of a jQuery book and I'd like to >> create a page or two of simple jQuery ajax in the context of couch. >> >> Starting from a bare $.ajax call level is useful - the syntactic >> sugar of jQuery is actually very useful - I just found it way too >> much all at once to also assimilate the plug in concepts as well. >> >> Additionally getting the paths straightened out when adding your own >> libs or using the internal ones is another thing. >> >> Perhaps a tutorial db that comes with couch and has a bunch of sample >> docs, simplest to more complicated, with libs, attachments, sample >> data would be useful. >> >> I remember when I was at Sybase ( it is still true ) they had a >> "pubs" sample database that was installed with the server and was >> useful in learning an in testing. Sybase training classes were based >> on the "pubs" database as well. I know the test data base is >> supposed to be similar but a testing environment is not always >> conducive to learning for many people. I'd like to float the idea of >> a database with sample data, code and docs that can be replicated >> from couch.io, or just comes with couch ( to save couch.io the >> bandwidth charges ). >> >> In the meanwhile I can start something on the wiki - in my copious >> spare time. >> > > I'm fairly I intrigued by the idea of a standard test database. At the > moment all tests build up their required test data. There could be a > couple issues in terms of mechanics but having a couple example > databses that could be cloned or some such might end up making tests > quite a bit more straight forward. > > Anyone else have thoughts? > Note I am NOT saying standard TEST database - although that is also a good idea. I am saying a standard tutorial database with examples of good and bad practice etc. the needs of tutorial databases may intersect with but are not identical to the needs of a testing database. For instance coverage is more important in a set of tests and tests are necessarily atomic but clarity and ease of understanding of how to compose concepts to build more featureful code is far more important in a tutorial database. A test database can be a starting point but I suggest we need more than that. So both are needed and I would be somewhat disappointed if my suggestion got taken to mean that there should be a standard test database alone. Nothing against the test code, but just sayin ...... Nitin >> >> Paul, thanks again for putting up with the noise while I stumbled >> around the basement banging my head everywhere. >> >> >> Nitin >> >> >>> Paul >>> >>>>>> Nitin >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>> >>