Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Support stale=update_after #6
I know this one follows CouchDB's implementation for the single server case, but I'd like to see a version that triggers a view build by simply sending a message to the view group instead of spawning a process to request an updated group. The process isn't going to do anything with the group, it's just going to sit there taking up resources while the view builds. Adding a cast handler to the view group should allow us to accept an unlimited number of stale=update_after requests during the lifetime of a build without crashing.
I merged that commit to master and also squashed the work in this request down to a single commit. I think it's ready to go in, just trying to decide what makes the most sense in re pull requests. This pull request will be automatically closed if a) we merge the branch or b) we rebase on top of master and then do the fast-forward merge. I don't think a simple cherry-pick will do the automatic close thing.