couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chris Anderson <jch...@apache.org>
Subject Re: roadmap 0.11/1.0
Date Sun, 01 Nov 2009 22:07:23 GMT
On Sun, Nov 1, 2009 at 1:59 PM, Jan Lehnardt <jan@apache.org> wrote:
>
> On 1 Nov 2009, at 19:48, Chris Anderson wrote:
>>
>> cron / event / changes handler
>>
>>  Applications need to be able to trigger functionality in a periodic
>> or event-based way. We could probably piggyback on _changes heartbeat
>> to provide cron + event services. The idea is a design document
>> function ("event" or "cron" or maybe "trigger") that is called once
>> for each item in the changes feed.
>>
>>  This is the one I'm least sure about, but I've heard a lot of people
>> request it. It's problematic because cron functionality isn't that
>> useful unless it has side-effects, which brings the whole sandbox/http
>> question up again.
>
> We need this for 0.11 to allow continuous replication to survive
> server crashes. While we are at it, we should add means to
> trigger compaction periodically or when certain limits are
> reached (IIRC Adam mentioned a waste-factor for databases
> to see when compaction is worth triggering). This would be
> the first thing I'd start working for new features.
>
> We also have a few open ends in the API that need
> consolidation. e.g. making the show/list/update handler
> more RFC2616 aware (sending Location e.g.). There's a
> few more of these. We should probably work on them before
> working on new half-baked features :)
>

Maybe the way to add the cron api is very modest. Eg, skip pushing it
out the design doc, but make it easy for people to configure some
erlang based handlers for events - compaction, replication, view
updates, etc.


> --
>
> Furthermore, more etap tests and a benchmarking suite
> would be great.
>
> Cheers
> Jan
> --
>
>
>
>
>>
>> rewriter
>>
>>  There's getting to be a pretty common pattern where people write
>> CouchApps and then deploy them behind a rewrite proxy. We've already
>> got rewrite patches floating around. It's just a matter of making the
>> API decisions.
>>
>> clustering
>>
>>  I've heard Cloudant has some clustering code, I'd definitely be
>> willing to help with integration, and I'm sure there are other people
>> who would as well.
>>
>>
>> Cheers,
>>
>> Chris
>>
>>
>> On Sun, Nov 1, 2009 at 7:02 AM, Benoit Chesneau <bchesneau@gmail.com>
>> wrote:
>>>
>>> was sent on user@ sorry for crossposting .
>>>
>>>
>>> ---------- Forwarded message ----------
>>> From: Benoit Chesneau <bchesneau@gmail.com>
>>> Date: Sun, Nov 1, 2009 at 3:44 PM
>>> Subject: roadmap 0.11/1.0
>>> To: user@couchdb.apache.org
>>>
>>>
>>> Hi all,
>>>
>>> http://couchdb.apache.org/roadmap.html hasn't been updated. And in
>>> fact i'm really curious. What is the next things on the roadmap ? Also
>>> damien spoke in june to have a fixed release schedule (one every 6
>>> months ?) is it still something in view ?
>>>
>>> - benoit
>>>
>>
>>
>>
>> --
>> Chris Anderson
>> http://jchrisa.net
>> http://couch.io
>>
>
>



-- 
Chris Anderson
http://jchrisa.net
http://couch.io

Mime
View raw message