jongleberry

API

12

right now it's `push(res, [path], [options], [priority])` which has too much arity. i'm thinking about making it fluent, something like: ``` js spdy(res).push(path) .priority(7) .send(new Buffer(1024)) .acknowledge( err => )...

multipart parsers?

9

like busboy and multiparty

talks

7

we should have a section of talks the team does related to jshttp / backend js frameworks

request-body

1

or whatever it's called to basically wrap `raw-body` with HTTP stuff

jshttp/security.md

5

i'd like to make a repo for common jshttp security issues, examples/tests, and fixes. @dougwilson you interested in helping?

google analytics

5

@dougwilson @Fishrock123 did one of you guys get a domain already? want to setup google analytics for all our team pages? main thing is that i don't like how it's...

like https://github.com/visionmedia/node-ratelimiter

migrated from https://github.com/koajs/koa/issues/101

need docs that isn't part of koala as i haven't touched koala in a while

look into passing `next` into each function

2

like regular middleware. might be needed to support https://github.com/koajs/path-match/issues/14 still think it's an anti-pattern MOST of the time since your logic should be refactored into functions, not middleware.