couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Paul Davis <paul.joseph.da...@gmail.com>
Subject Re: New Externals: Implemented with tests
Date Tue, 12 Oct 2010 04:03:23 GMT
At the urging of Randall Leeds I added another convenience.

Your os_daemons can now register to be restarted when the
configuration changes. This lets os_daemon processes automatically
upgrade themselves if they so desire.

Branch is at: http://github.com/davisp/couchdb/commits/new_externals/
The commit message has a description here:

http://github.com/davisp/couchdb/commit/653ed6dd3dea87357a90c66b612568a5a9cb6f00

The commit is not stable. I'm forcibly pushing so it'll change. But
it'll be the second most recent on the new_externals branch as long as
that branch is alive.

Paul Davis


On Mon, Oct 11, 2010 at 5:45 PM, Ryan C. Hill <rch@computer.org> wrote:
> I'd like to see it in both as well. Exciting feature.
>
> Flexible on 1.1 inclusion though. It is brand-new code after all.
>
> -R
>
>
> ----
> From: "Robert Newson" <robert.newson@gmail.com>
> To: dev@couchdb.apache.org
> Cc:
> Subject: Re: New Externals: Implemented with tests
> Date: Mon, 11 Oct 2010 16:23:04 -0500
>
> I'd love to see it on trunk and in 1.1.
>
> B.
>
> On Mon, Oct 11, 2010 at 10:15 PM, Paul Davis
> <paul.joseph.davis@gmail.com> wrote:
>> Just a progress update. The HTTP proxy is now capable of running the
>> entire Futon test suite with only two failing tests. The http.js test
>> fails because its asserting an exact URL structure, where as running
>> through the proxy adds a path component. The other failing test is the
>> stats module. Because I just make CouchDB proxy to itself, the five or
>> so assertions on request counts fail because each request is causing
>> the stat to be incremented twice (which is to be expected).
>>
>> I'm quite happy with how the current status of things.
>>
>> What do people think about committing this? I think someone said to
>> wait till after 1.1.0 is released but I'm not changing any behavior of
>> the existing _external's API. Its still there completely intact so we
>> wouldn't be breaking anything people may currently rely on. Adding it
>> before 1.1 would give more people a chance to start using this in the
>> wild with crazy broken HTTP clients to find the remaining edge cases.
>>
>> Feedback desired.
>>
>> Paul Davis
>>
>
>
>

Mime
View raw message