On Wed, Apr 17, 2013 at 7:55 AM, Stephen Bartell snbart...@gmail.com wrote:
But for what I was doing, no, I wasn't specifying since. I would expect the
fundamentals to be the same as well. What I was see is that even without
`since` given, no changes would come through until that second
Ok heres a test script. Have a couch serving localhost:5984 in admin party
mode.
git clone https://github.com/snbartell/couch-es-test.git
cd couch-es-test
npm install
node index.js
My theory of a second source crashing couch was wrong.
I think I know whats going on. My script above acts just
Setting timeout and heartbeat to the same value is going to lead to
exactly what you're seeing.
The timeout setting is how long, without an event, the connection will
stay open.
The heartbeat setting is how long to wait, without an event, before
sending a newline character to keep the connection
Hey guys,
Just following up on this, as it's been five days. And I can't move ahead
without help.
At a minimum, we need to create the 1.4.x branch. But I'd really like for
us to properly document our merge procedure (which has languished because I
don't know Git well enough to fill out the
On Wed, Apr 17, 2013 at 3:45 PM, Noah Slater nsla...@apache.org wrote:
At a minimum, we need to create the 1.4.x branch. But I'd really like for
us to properly document our merge procedure (which has languished because I
don't know Git well enough to fill out the details) and then for us to
So that features can be merged into it as they become ready.
Check out:
http://wiki.apache.org/couchdb/Merge_Procedure
Thoughts?
On 17 April 2013 14:47, Dirkjan Ochtman dirk...@ochtman.nl wrote:
On Wed, Apr 17, 2013 at 3:45 PM, Noah Slater nsla...@apache.org wrote:
At a minimum, we need
On Wed, Apr 17, 2013 at 4:02 PM, Noah Slater nsla...@apache.org wrote:
So that features can be merged into it as they become ready.
Check out:
http://wiki.apache.org/couchdb/Merge_Procedure
Thoughts?
Seems like you could call the next-feature-release branch master,
and not have to start a
The goal was that you only merge in features when they are ready, and come
with tests, and docs, and what have you. And that you actually call a lazy
consensus merge request on dev@ before you can merge in.
On 17 April 2013 15:18, Dirkjan Ochtman dirk...@ochtman.nl wrote:
On Wed, Apr 17,
I'll let someone more familiar with Git, and the conversations we had
around this, answer.
To be honest, I am less interested in debating the specifics of the
proposal than I am about actually getting a proposal agreed upon, and
putting it into practice. We are a little over a week away from the
Members present: jan, ryan_ramage, Humbedooh, Wohali, benoitc, drsm79,
wendall911, rnewson, TheJH
Meeting summary:
1. Preface
2. TheJHâs Security Proposal
3. action items from last week
IRC log follows:
# 1. Preface #
19:10:37 [Humbedooh]: ACTION
Thanks for the summary Robert. That clears it all up :)
Ok so now I'm going to risk looking like a tool. Besides the underlying
mechanism, what is the difference between eventsource and continuous? In other
words, what does ES bring to the table that continuous does not? I was
originally
11 matches
Mail list logo
