:25:01 PM
Subject: Re: [DISCUSS] Deprecating _externals?
Hi Joan,
one reason why I've never missed an official plugin API is that
CouchDB provides the externals API, which is documented and works well.
Please see my further comments inline.
Today, someone came to the #couchdb channel
Hi Joan,
Thanks for pushing this forward, replied inline.
On Mon, Oct 27, 2014 at 11:58 PM, Joan Touzet woh...@apache.org wrote:
Today, someone came to the #couchdb channel asking about
_externals. For a long while it's been on my mind that perhaps
we should deprecate the entire _externals
Hi Joan,
one reason why I've never missed an official plugin API is that
CouchDB provides the externals API, which is documented and works well.
Please see my further comments inline.
Today, someone came to the #couchdb channel asking about
_externals. For a long while it's been on my mind
. the Fallacies of Distributed Computing.
-Joan
- Original Message -
From: Klaus Trainer klaus_trai...@posteo.de
To: dev@couchdb.apache.org
Sent: Tuesday, October 28, 2014 9:25:01 PM
Subject: Re: [DISCUSS] Deprecating _externals?
Hi Joan,
one reason why I've never missed an official
Today, someone came to the #couchdb channel asking about
_externals. For a long while it's been on my mind that perhaps
we should deprecate the entire _externals feature for a number
of reasons:
1. Couch is not a great reverse proxy. Making it into one is
as hard as rewriting nginx or
They've always been a bit of an odd beast. In hindsight the best
solution would've to remove the daemons/externals APIs altogether when
the changes feed was introduced. I agree that they'll make little to
no sense in a cluster, plus once you get around to managing a cluster
adding the
