this may well break a lot of code that uses the http library so it may
be better to make a separate headersarray property on the http client
function instead.
any thoughts?
usage:
instead of parsing through the headers in the response, you can now
iterate them as an array:
e.g
res.headers["set-cookie"].forEach( function( cookie ) {
props = cookie.split(";");
};
The problem is that it breaks the multipart library. I've pinged
Felix to look at it, but haven't heard from him, and I haven't had a
chance to thoroughly comb through the issues myself.
The branch is here: http://github.com/isaacs/node/commits/jsgi-header-fast
The benefit of this is that node would take the same structure for the
header object that JSGI specifies. The only thing standing in the way
is the multipart parsing incompatibility.
--i