Skip to content


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP


Patching http.serverResponse ?! #814

andreineculau opened this Issue · 3 comments

2 participants

Andrei Neculau TJ Holowaychuk
Andrei Neculau

I've only now became aware that connect is patching the prototype of http.serverResponse in

Surely there are better ways than that.

TJ Holowaychuk
tj commented

not really, node core has inadequate support for many things, similar should be in core if it's to be useful for anyone else

TJ Holowaychuk tj closed this
Andrei Neculau

I can only agree with you that node's core/http has issues, but those should be solved in node's codebase, rather than in monkey-patches (with inadequate support themselves -- e.g. just blindly attaching a charset param to content-type; maybe it already has one).

There's a reason why people say no to Prototype.js ...

TJ Holowaychuk
tj commented

they certainly should be, but we can't wait around for core to finally figure out that it's not useful. It took roughly a year to get .setHeader() etc in when I said writeHead was too inflexible, it'll be another year before things like this get in if ever

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.