Removed logic breaking returning of JSON content

[naugtur]

There is no documentation for a send function in node's HTTP, so I assume it's supposed to be Express response.
Anyway, I have never seen a call to .send with a response object passed as argument in any documentation. On the other hand it breaks passing objects (intended as json responses) to the .send method if they have a field called body.

[alanjames1987]

I'll take a look at your pull request as soon as I can. I just wanted to confirm I received it.

[howardabrams]

Hey Alan, where did we leave off with this pr?

[alanjames1987]

I didn't get a chance to look over the pull request. I won't have time to until this weekend.

[estilles]

@howardabrams / @alanjames1987, @naugtur is correct. If the argument passed to res.send() is an object, Express does not check the object for status codes or use only the body key when present. This is definitely a deviation from Express' implementation.

When Express' res.send() encounters an object it actually passes it directly to res.json() (which in turn stringify's it and passes it to res.send()).

@naugtur's PR set's _data to the passed object, instead of passing it to .json(), which is also inconsistent with Express' implementation.

While we definitely need to address @naugtur's concerns, this PR should not be merged as-is.

[estilles]

This issue should be take care of once we roll out release 2.0 (see our Roadmap to Release 2.0, issue #54).