Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of rizenine@gmail.com designates
 209.85.211.174 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=myv9EfbVGREqVh34BnRoEbdErHAbPo+x93vMcyk3axYIfEuLSrx1FCTTxDv5eKt2jw
         KAxdDsw+dhFI7MAWgqyy7rF1SNCCQzjaqvwiYFmSfMOq0gsvAcGlORVBl1V33rCodCVB
         SLDP1JOlA1xpDo/ZLa3u3y0zPQJ/GA6scuD7w=
MIME-Version: 1.0
In-Reply-To: <7db9abd31003100649x4e7d3443kfc4874d1a9e24406@mail.gmail.com>
References: <3887f8451003100639t105264ddh69502a9f124140fe@mail.gmail.com>
	 <7db9abd31003100649x4e7d3443kfc4874d1a9e24406@mail.gmail.com>
Date: Wed, 10 Mar 2010 11:24:38 -0500
Message-ID: <3887f8451003100824x5c51d5bq439e3d822ee7539a@mail.gmail.com>
Subject: Re: Server Side Language Confusion
From: Justin Stanczak <rizenine@gmail.com>
To: user@couchdb.apache.org
Content-Type: multipart/alternative; boundary=0016368e2acc137f96048174bc82

--0016368e2acc137f96048174bc82
Content-Type: text/plain; charset=ISO-8859-1

Ya, I've looked at Helma before. Can the included DB stuff be removed easy
enough? I don't know much about it. I'm open to look at any language.

On Wed, Mar 10, 2010 at 9:49 AM, kowsik <kowsik@gmail.com> wrote:

> Helma or node.js both work naturally with Couch. They are both
> JavaScript servers and so getting and posting documents while sending
> them upstream to the browser become very natural with little or no
> translation. If you combine this with something like Sammy
> (http://code.quirkey.com/sammy/) and jQuery, you can very rapidly
> build a RESTful app with the rendering all on the browser side.
>
> Regards,
>
> K.
>
> On Wed, Mar 10, 2010 at 6:39 AM, Justin Stanczak <rizenine@gmail.com>
> wrote:
> > I'm having a little trouble figuring out what to select as the server
> side
> > language for accessing CouchDB. I'm new to CouchDB so this paragraph will
> be
> > a long list of questions and sentences of how I understand things to this
> > point in time. Please feel free to correct me and help me better learn. I
> > like the idea of eliminating all the DB mapping and focus on programming
> > again, that CouchDB allows you to do. So I guess the first issue is you
> > don't want your CouchDB exposed to the WWW, so you need a HTTPD to act as
> a
> > proxy, via some language. This language would provide the session
> tracking.
> > That session tracking would give you user logins and what not. This would
> > also restrict access to your CouchDB, as I don't see CouchDB has much in
> the
> > way of protection when it comes to access control to it's databases. This
> > leads to the issue of Javascript not being the language of choice for
> client
> > side, as you really don't want clients, duh. So now that's where my
> language
> > server side question comes from. What's a good option when using CouchDB?
> I
> > know everyone has their opinions, but really, if you are using CouchDB as
> > your back end database what language has been developed the most with
> > CouchDB? What works the best? Surely there is one that stands out over
> the
> > rest? Maybe I'm way off, any input is welcome, thanks.
> >
>

--0016368e2acc137f96048174bc82--