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 whachoe@gmail.com designates
 209.85.218.221 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type;
        b=A43l3wmLK0FdRnlycNPVcfP6U3ww+SPdm0krzfmC8GZxny5Zp3HuHQJdsOf10AOhLq
         RWEU0gfpIBZteGbRpqKRIIJLwinZQGEyTe7dE/T5AzQIMDJzswNjqZycCEmvrscKJN5e
         fjlqLlohbrouQAPF8KipHpCsUOIgOC+H411M0=
MIME-Version: 1.0
In-Reply-To: <3887f8451003100639t105264ddh69502a9f124140fe@mail.gmail.com>
References: <3887f8451003100639t105264ddh69502a9f124140fe@mail.gmail.com>
From: Jo Giraerts <whachoe@gmail.com>
Date: Wed, 10 Mar 2010 15:54:48 +0100
Message-ID: <39d31cdc1003100654i57c3be17y59c1f43c2e480297@mail.gmail.com>
Subject: Re: Server Side Language Confusion
To: user@couchdb.apache.org
Content-Type: multipart/alternative; boundary=00032555f2be9fc9510481737d9e

--00032555f2be9fc9510481737d9e
Content-Type: text/plain; charset=UTF-8

In my case, i'm doing the development in PHP with a custom session-handler
that also uses couchdb as session-storage.
But couchdb is language-agnostic and since it's completely http-rest, you
can access it from any language that lets you access an url and is capable
of handling json - which is probably any language still in use today. So, my
humble advice is just go with whatever language you are comfortable with ;-)
if you're interested in my couchdb-session-handler, it's on github:
http://github.com/whachoe/Couchdb-PHP-Session-Handler


On Wed, Mar 10, 2010 at 3:39 PM, 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.
>

--00032555f2be9fc9510481737d9e--