jongleberry

@dougwilson what do you think about integrating this now?

@dougwilson or are you still planning to release a `trust` module?

:+1:

o i c. proxy-addr doesn't do as much as i thoguht it would in its current form. right now, the benefit is minimal. - https://github.com/jshttp/forwarded/pull/1 - parse all `X-Forwarded-*` headers...

how about something like `.log('some.event', obj)`, then have something like `app.trace(fn*)` middleware that hook on these events? instead of wrapping all the middleware, which probably won't give us exactly what...

well you don't want every middleware to trace stuff. that would get too noisy. just the important ones. which is why i prefer something like `.log()` where you only log...

oh i've never seen middleware stuck. lol. it's too much stuff if you put them everywhere, but i don't think you need to put them everywhere. ex, logging the response...

yeah i'm just thinking of a more generic solution. here's what i'm thinking right now: ``` js function compose(middleware){ return function *(next){ var i = middleware.length; var prev = next...

similarly, i don't see the need to limit it only to when the middleware starts and ends. i'm not sure how your branch works now, but i'd like to hook...

ya i'm just trying to somewhat combine them because i don't see how they are totally different.