On Thu, Sep 17, 2009 at 1:05 AM, Curt Arnold wrote:
> Sorry about the bad quoting, somehow the message evaded my email client.
>
> Paul Davis wrote:
>
>>
>> I'm not really concerned with major user agents in terms of headers we
>> add. Most of those should be configured to do the right thing 99%
Sorry about the bad quoting, somehow the message evaded my email client.
Paul Davis wrote:
I'm not really concerned with major user agents in terms of headers
we add. Most of those should be configured to do the right thing 99%
of the time regardless. The question is what would I do if I
On Wed, Sep 16, 2009 at 10:26 PM, Curt Arnold wrote:
>
> On Sep 16, 2009, at 5:42 PM, Chris Anderson wrote:
>
>> On Wed, Sep 16, 2009 at 3:04 PM, wrote:
>>>
>>> Author: jchris
>>> Date: Wed Sep 16 22:04:18 2009
>>> New Revision: 815984
>>>
>>> URL: http://svn.apache.org/viewvc?rev=815984&view=re
On Wed, Sep 16, 2009 at 6:42 PM, Chris Anderson wrote:
> On Wed, Sep 16, 2009 at 3:04 PM, wrote:
>> Author: jchris
>> Date: Wed Sep 16 22:04:18 2009
>> New Revision: 815984
>>
>> URL: http://svn.apache.org/viewvc?rev=815984&view=rev
>> Log:
>> include_docs now take an _id (as well as a _rev) in
Noah,
Blocker fixed. Apologies for holding you back a day.
Paul
On Tue, Sep 15, 2009 at 4:54 PM, Paul Davis wrote:
> On Tue, Sep 15, 2009 at 6:00 AM, Noah Slater wrote:
>> Hey,
>>
>> I plan on cutting the 0.10 release for a vote today.
>>
>> I would like to collect any objections now before I
[
https://issues.apache.org/jira/browse/COUCHDB-504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12756360#action_12756360
]
Paul Joseph Davis commented on COUCHDB-504:
---
Doh, I forgot the origin of the tic
[
https://issues.apache.org/jira/browse/COUCHDB-396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Joseph Davis resolved COUCHDB-396.
---
Resolution: Fixed
Fix Version/s: (was: 0.10)
0.11
Fixe
[
https://issues.apache.org/jira/browse/COUCHDB-504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Joseph Davis resolved COUCHDB-504.
---
Resolution: Fixed
Fix Version/s: 0.11
Fixed as of r816033.
Someone tell me w
On Sep 16, 2009, at 5:42 PM, Chris Anderson wrote:
On Wed, Sep 16, 2009 at 3:04 PM, wrote:
Author: jchris
Date: Wed Sep 16 22:04:18 2009
New Revision: 815984
URL: http://svn.apache.org/viewvc?rev=815984&view=rev
Log:
include_docs now take an _id (as well as a _rev) in the emitted
value, t
On Wed, Sep 16, 2009 at 3:04 PM, wrote:
> Author: jchris
> Date: Wed Sep 16 22:04:18 2009
> New Revision: 815984
>
> URL: http://svn.apache.org/viewvc?rev=815984&view=rev
> Log:
> include_docs now take an _id (as well as a _rev) in the emitted value, to
> load docs other than the one doing the e
+1 for single line logs. Not having the returned status code on the
same line makes debugging logs quite a bit more difficult.
On Wed, Sep 16, 2009 at 1:06 PM, Adam Kocoloski wrote:
> Hi Damien, I'd _really_ still like to revert to one line in the logfile for
> a request/response pair. I believe
Hi Damien, I'd _really_ still like to revert to one line in the
logfile for a request/response pair. I believe this patch does the
trick; if you don't object I'll apply it. Best,
Adam
diff --git a/src/couchdb/couch_httpd.erl b/src/couchdb/couch_httpd.erl
index 3518481..0c467d5 100644
--- a
On Sep 16, 2009, at 9:31 AM, Jan Lehnardt wrote:
On 16 Sep 2009, at 15:24, Adam Kocoloski wrote:
On Sep 16, 2009, at 8:44 AM, Jan Lehnardt wrote:
On 16 Sep 2009, at 14:21, Adam Kocoloski wrote:
On Sep 16, 2009, at 4:00 AM, Brian Candler wrote:
Does this make any sense to you? It looks lik
Erlang code path prefers older versions of CouchDB
--
Key: COUCHDB-505
URL: https://issues.apache.org/jira/browse/COUCHDB-505
Project: CouchDB
Issue Type: Bug
Affects Versions: 0.11
On 16 Sep 2009, at 14:15, Curt Arnold wrote:
Wrote Jason Davies
Interesting, why did it affect OAuth? OAuth shouldn't care about
what's in the request body as it only operates on the request
headers. Thanks, -- Jason Davies
Sorry, just the related tests fail (and apparently for good ca
On 16 Sep 2009, at 15:24, Adam Kocoloski wrote:
On Sep 16, 2009, at 8:44 AM, Jan Lehnardt wrote:
On 16 Sep 2009, at 14:21, Adam Kocoloski wrote:
On Sep 16, 2009, at 4:00 AM, Brian Candler wrote:
Does this make any sense to you? It looks like it's reading
couch.beam from
couch-0.11.0a8156
On Wed, Sep 16, 2009 at 1:38 AM, Curt Arnold wrote:
>
> On Sep 15, 2009, at 10:44 PM, Paul Davis wrote:
>>
>> Regardless of browser support, the first question should always be
>> weather we can avoid hacks specific to a user agent. Unless you can
>> show that there's a case where its absolutely i
Kevin,
Thanks for rounding this up. That's pretty much the conclusion I cam
to but in quite a bit more concise form.
A while ago I put in a ticket for infra@ to start a build bot
instance. Gavin McDonald has been taking care of build-bot requests
and has said that he'll set that up for us.
Thank
On Sep 16, 2009, at 8:44 AM, Jan Lehnardt wrote:
On 16 Sep 2009, at 14:21, Adam Kocoloski wrote:
On Sep 16, 2009, at 4:00 AM, Brian Candler wrote:
Does this make any sense to you? It looks like it's reading
couch.beam from
couch-0.11.0a815641 (correct), but couch.app from
couch-0.9.0a7672
Wrote Jason Davies
Interesting, why did it affect OAuth? OAuth shouldn't care about
what's in the request body as it only operates on the request
headers. Thanks, -- Jason Davies
Sorry, just the related tests fail (and apparently for good cause).
Adam Kocoloski commented on COUCHDB-345:
On 16 Sep 2009, at 14:21, Adam Kocoloski wrote:
On Sep 16, 2009, at 4:00 AM, Brian Candler wrote:
Does this make any sense to you? It looks like it's reading
couch.beam from
couch-0.11.0a815641 (correct), but couch.app from
couch-0.9.0a767213 (?!).
Bingo, there's the problem. It looks l
On Sep 16, 2009, at 4:00 AM, Brian Candler wrote:
Does this make any sense to you? It looks like it's reading
couch.beam from
couch-0.11.0a815641 (correct), but couch.app from couch-0.9.0a767213
(?!).
Bingo, there's the problem. It looks like Erlang's code loader wasn't
prepared for doub
On Sep 16, 2009, at 4:16 AM, Brian Candler wrote:
On Tue, Sep 15, 2009 at 09:22:41PM -0400, Adam Kocoloski wrote:
Heh, I stand corrected. +1 on the path forward. I guess its just a
matter of adding Connection: Keep-Alive to the response headers.
You're quite right that HTTP/1.0 (RFC 19
On Wed, Sep 16, 2009 at 11:58 AM, Robert Newson wrote:
> Since HTTP 1.0 has no Connection header at all, the proposal "breaks"
> http 1.0 either way, whether we choose "Keep-Alive" or "close". Given
> that, "Keep-Alive" seems the better choice. The defined behavior for
> http 1.0 is that the conne
Since HTTP 1.0 has no Connection header at all, the proposal "breaks"
http 1.0 either way, whether we choose "Keep-Alive" or "close". Given
that, "Keep-Alive" seems the better choice. The defined behavior for
http 1.0 is that the connection is closed after every request, so we
either stick with tha
I have a patch to send_json that echos the Connection header if
defined, that seems to fix the issue. I'll attach it to the ticket as
a starting point
On Sep 15, 2009, at 9:22 PM, Adam Kocoloski wrote:
Heh, I stand corrected. +1 on the path forward. I guess its just a
matter of adding
Hi,
I've had a look into the options available at apache for setting up ci
for couch.
http://ci.apache.org contains 4 options:
* Gump
* Buildbot
* Hudson
* Continuum
1 - Gump is more about continually integrating projects together. It
takes the head of each repository and attempts to build them
On 16 Sep 2009, at 10:05, Brian Candler wrote:
On Tue, Sep 15, 2009 at 11:30:37AM -0700, Chris Anderson wrote:
The basic tradeoff here is between safety and speed. With a simple
benchmark on my Mac laptop (OSX 10.5) delayed_commits gives ~230
writes/second while we only get about 5/sec with th
On Tue, Sep 15, 2009 at 09:22:41PM -0400, Adam Kocoloski wrote:
> Heh, I stand corrected. +1 on the path forward. I guess its just a
> matter of adding Connection: Keep-Alive to the response headers.
You're quite right that HTTP/1.0 (RFC 1945) doesn't support persistent
connections, and doesn'
On Tue, Sep 15, 2009 at 11:30:37AM -0700, Chris Anderson wrote:
> The basic tradeoff here is between safety and speed. With a simple
> benchmark on my Mac laptop (OSX 10.5) delayed_commits gives ~230
> writes/second while we only get about 5/sec with the slow safe option.
>
> I think 5 writes/seco
On Tue, Sep 15, 2009 at 10:46:06AM -0400, Adam Kocoloski wrote:
> The first thing I'd wonder is whether
> those couch-0.XX.0aXX were accidentally named in such a way (by us)
> that the Erlang code loader was searching older builds with higher
> priority
Unfortunately I didn't keep a copy
Hey Curt,
On 16.09.2009, at 07:38, Curt Arnold wrote:
The spec appears to be walking a fine line with respecting behavior
of some HTTP 1.0 caches that treated expires in the past as
equivalent to no-cache. See section 14.9.3, where HTTP 1.1 caches
are instructed to assume no-cache if they
[
https://issues.apache.org/jira/browse/COUCHDB-257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christopher Lenz reopened COUCHDB-257:
--
Oops, turns out I got this wrong. As Curt explains on the mailing list, adding
an Expires
33 matches
Mail list logo
