Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of bchesneau@gmail.com designates
 209.85.214.180 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:content-transfer-encoding;
        b=rwMHK8MZDRXAsTijgpU1eedQIRr2MCgJV2Uc5OfoEA2m+7Ly18e4A6TEBXVlvD/ZVd
         HV25oKo0HoCWyqi7KcVdBWyKsBmeN6x2ZaDp2KO5P3ZyxxbQaixpHknB962KnY377h87
         YtsFCDaU5gaiGFV831bj8n7erv/Ta8PPR5PMM=
MIME-Version: 1.0
In-Reply-To: <AANLkTikedjDQhCncXTEmedGhtNu9C_Pf06Nh3DKnPfQV@mail.gmail.com>
References: <AANLkTin5CXFZa5wNvE2Y15Kn-Uh_Cn9sUwXiY92ZAphS@mail.gmail.com>
	<85867503-84A2-4EB3-9AB4-46CA6652A7B4@apache.org>
	<41DCB3BF-BDC6-48C3-A435-3DBD10804B8F@apache.org>
	<AANLkTikedjDQhCncXTEmedGhtNu9C_Pf06Nh3DKnPfQV@mail.gmail.com>
Date: Sat, 22 Jan 2011 11:27:45 +0100
Message-ID: <AANLkTim0KOfducERv-4m2oPACvDbXcb+O6KGZ96QiQFC@mail.gmail.com>
Subject: Re: code style
From: Benoit Chesneau <bchesneau@gmail.com>
To: dev@couchdb.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Thu, Jan 20, 2011 at 4:16 PM, Paul Davis <paul.joseph.davis@gmail.com> w=
rote:
>> I would like to see, before getting started on any of this, an RFC-style=
 document / wiki page that defines what a CouchDB plugins system looks like=
 that we agree on implementing.
>>
>
> If this were any/most other languages I would totally agree. Except
> Erlang is kinda laissez-faire when it comes to calling bits of code.
>
> Regardless of what the "plugin" system ends up looking like, it'll
> basically be the same API that's used all over couchdb internals.
> It'll be self-automatically stable once we make it not suck.
>
> *After* there's a system in place that allows plugins to exist without
> a carnal knowledge of the code base I think it would be good to
> explicitly formalize what we support as a plugin but until then we
> just don't make any claim of supporting anything as we start adding
> and organizing in preparation.
>

Imo the thing we could have in view, except this plugin "support", is
a simple api to call any part of couchdb we need. Something as simple
as the HTTP api but for erlang.

 I'm thinking to have a couchbeam pure erlang api for example just for
that. It would also help us to make new HTTP layer using webmachine
for example or anything. fabric an hovercraft are also good
inspiration. I'm pretty ready to do such thing. Does it worth a thread
to discuss about it?

- beno=EEt