Re: CouchDB data processing endpoints

Hi Robert, As long as design documents have meaningful processing endpoints, they will remain the extremely useful babel fish of CouchDB. Does your "for some time to come” mean that you support a LTS for 3.0? (ref Jan 19 Aug 2019) Johs > On 8 Sep 2019, at 16:24, ermouth wrote: > > Hi. >

Re: [NEWS] The CouchDB weekly news for May 19 is out!

> On 20 May 2016, at 19:33, Matthew Rijk wrote: > > How do i unsubscribe to this Click dev-unsubscr...@couchdb.apache.org

Re: [PROPOSAL] CouchApp Work Group

Good luck, Alexander I have some articles under development that I hope will help the discussion on how to use Couchapps to expand the CouchDB ecosystem. johs > On 31 Oct 2015, at 15:35, Michelle Phung wrote: > > :) i think its a really good idea! > > Michelle >

Re: [PROPOSAL] Allow rewrites to be JS function

uld rather let the Node.js and Go web libraries serve content and >>> let us focus on building a clustered replicating database. We will draw >>> more people to this community if we can do that properly over creaky, >> slow >>> and limited web serving mashed on top of a dat

Re: [PROPOSAL] Allow rewrites to be JS function

Thanks Andy, I will try and get some use cases up on confluence. As for whoever would pick up the work after ermouth, I have of course one big thing on the wish list that goes well with a new router solution.. reverse proxy I remember asking about it when I first started to work w CouchDB and

Re: CouchDB _rewrite

e need to > get it out the door, it is far overdue. > > Looking at changing basic functionality like _rewrite can come after > 2.0 is done, in the 3.0 timeframe. > > -Joan > > - Original Message - >> From: "Johs. E" <j...@b2w.com> >> To:

CouchDB _rewrite

Fellow CouchDB enthusiasts, Let me quote a dialogue I had the other day with a colleague on Couchapps and _rewrite: > > I would like to know what is so horrible with the vhost/rewrite of CouchDB > You must concentrate all rules in one place, that is totally out of idea ‘one > app – one ddoc’ >