Gregg Caines

The purpose of that res.status interface is for when you're happy with the defaults. If you want to do something else, plain node is still pretty simple: ``` res.statusCode =...

Thanks! Any chance you can write a test for this scenario as well?

@hans-d @devoncrouse Good for production use already? Should I add a link from our README?

Hey...Sorry about the slow response... I've been busy with other work lately and wanted to think about this for a bit too. I think you're probably right about #2. I...

Nope... Sorry. We probably won't be the team to do it. We're just working on too many other things and this just isn't much of an itch for us anymore.

We looked at supporting 0.8 about a year ago when the first specs were coming out, and decided the differences were too significant. I can't recall specifically why now, but...

@jirwin We haven't moved on it at all, so we'd certainly entertain PRs. :) Have you got an idea for supporting 0.7 and 0.8 concurrently as well?

@jirwin @r4j4h I haven't got a huge amount of time to help these days, but I'm definitely interested, and if I can help, I will. Let me know if you...

We've seen that in a few scenarios, but it's tough for me to guess which one you're experiencing. Usually it happens when you give an incorrect offset in a fetch,...

Ohh... good question... Now that I look at the code, that bad-offset case is actually caught earlier. The exception in this case is one that should never be raised, so...