Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.1 \(1498\))
Subject: Re: CouchDB Plugins First Draft
From: Jan Lehnardt <jan@apache.org>
In-Reply-To: 
 <CAJNb-9rjTchKgj9CGPQj0Jjqfa4sWj4uXme_zDz+h-MrzFdfFA@mail.gmail.com>
Date: Thu, 1 Nov 2012 12:59:09 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <9BD90828-E701-45BC-8BF5-B7F49B282EED@apache.org>
References: <40BCC84F-C695-492E-B56E-08C60955A3D8@apache.org>
 <CAHdjipK3UOg3FbnA_sGUpcP8YXOa0PYfnn3Zx0JmTodPjJdu+A@mail.gmail.com>
 <CABvT1DFAcMQtx4WGBPwZwqRkNzVBFPCnFb_djirDtS_9RFJsFw@mail.gmail.com>
 <3B2D6B8E471743B49554B23F98B8414C@cloudant.com>
 <629F0E3A-6192-4555-90C9-379DA39E0161@dionne-associates.com>
 <CAJNb-9rjTchKgj9CGPQj0Jjqfa4sWj4uXme_zDz+h-MrzFdfFA@mail.gmail.com>
To: dev@couchdb.apache.org

Benoit,

Thanks a lot!

You bring up a lot of great material to the discussion along with your
expertise in writing and handling plugins in rcouch and related =
projects.

I=92ll comb through this thread and extract all relevant information =
into
the gist/wiki document.

This is all great stuff! :)

Jan
--=20


On Nov 1, 2012, at 11:17 , Benoit Chesneau <bchesneau@gmail.com> wrote:

> there are also other plugins around :
>=20
> https://github.com/benoitc/couch_randomdoc
>=20
> https://github.com/benoitc/couch_zmq wich is using erlzmq
>=20
> https://github.com/benoitc/couch_es
>=20
> https://github.com/refuge/bigcouch_spatial
>=20
> https://github.com/refuge/couch_dbupdates
>=20
> https://github.com/ocastalabs/CouchDB-XO_Auth
>=20
> ....
>=20
>=20
> So on erlang the situation is quite complex. As a free reminder when =
we
> spoke about rabbitmq plugins in january, nobody wanted that which let =
me
> perplex. Like I said do we we want a plugin system or just a way to =
load
> app?
>=20
> About couchdb-lucene for example it could be rewritten to use more of =
the
> internals of couchdb. And probably using jinterface instead of living
> externally so it could be better integrated.  (This is just an example =
of
> what could be done) . couch_es could be fully written in elixir or js =
and
> distributed as an internal couchapp. Same for random doc etc .
>=20
> Imo when we speak about plugins we should have in mind the of their
> deployement. This is one thing to install a plugin on a machine , =
another
> to make sure that this plugin is installed on others machines. And =
when I
> say other machines I'm not only speaking about machines in your lan =
(some
> of us have tools and people for that) but machines of remote possibly
> stranger people replicating your data . ANd this part is definitely =
not
> possible easily with something like rabbitmq plugins.
>=20
>=20
> - beno=EEt
>=20
>=20
>=20
> On Thu, Nov 1, 2012 at 11:01 AM, Bob Dionne =
<dionne@dionne-associates.com>wrote:
>=20
>> Reminds me of my favorite book - "Sketches of an Elephant"
>>=20
>> Jan, thanks for putting a stake in the ground, I've wanted to see =
this
>> forever. The proposal in my mind takes too much of a product =
management or
>> marketing view (perhaps knowingly). Here's how it will look the =
buttons one
>> will push, etc..
>>=20
>> I think the "what" and "how it works" are important to decide on =
first,
>> .eg. @rnewson's suggestion for something like RabbitMQ. Reading the =
docs
>> for that, the "what" is much clearer.
>>=20
>> Looking over the efforts to date, couchdb-lucene, and geocouch, these =
two
>> are quite different in terms of design, one is roughly loosely =
coupled, the
>> other more native (in the same VM). A plugin architecture, in my =
mind,
>> should emerge from the code refactoring and layout we're currently
>> discussing. We should ask and answer questions such as:
>>=20
>> 1. the role of externals
>>=20
>> 2 access to the storage layer (API?)
>>=20
>> 3. separation from http layer
>>=20
>> 4. support for code upgrades
>>=20
>> 5. balancing of resources
>>=20
>> I didn't mention Auth and Logging as I think these are separate in =
terms
>> of concerns, more system oriented. Whereas geocouch and =
couchdb-lucene are
>> actually extending the functionality in meaningful ways.
>>=20
>>=20
>> On Nov 1, 2012, at 5:30 AM, Simon Metson <simon@cloudant.com> wrote:
>>=20
>>> +1 - keep it simple for the first iteration.
>>>=20
>>>=20
>>> On Wednesday, 31 October 2012 at 23:40, Robert Newson wrote:
>>>=20
>>>> I quite like the rabbitmq approach (a lot like the apache httpd
>> approach).
>>>> you can enable/disable/list plugins but the tool doesn't include =
the
>>>> downloading and managed repository bits, which is a huge rabbit =
hole
>> (pun
>>>> intended).
>>>=20
>>>=20
>>>=20
>>=20
>>=20