Add API to easily send JSON as web response body

[fafhrd91]

we may need to reconsider adding "json=" parameter to web.Response class.

more discussions in #1726 and #592

[fafhrd91]

it is about convenience.

Of course for proper handling of json encoding with versioning and custom serialization proper middle should be used.

[fafhrd91]

@popravich @socketpair @kxepal @jettify

[alex-eri]

Why is this better than aiohttp.web.json_response?

[fafhrd91]

it is not better it is convenient.

[asvetlov]

It's like moving in backward direction.
web.Response is a class for sending either text or binary data back to client.

Honestly I have a feeling than the class is overcomplicated (take a look in Response.__init__ code).
For sake of clean architecture we need two classes: TextResponse and BinaryResponse.
But I can live with current state.

Adding a new parameter leads to combinatorial explosion.

[fafhrd91]

I am ok with this. we can close this ticket

[AraHaan]

I agree with @asvetlov on aiohttp needing 2 response classes and having the json response part of TextResponse. I would do it myself but I am not sure what parts are for binary data and what parts are for text data or both. That is how complicated it is. However there might be places where binary data is sent with json data. In that case it might break unless there is a way to avoid it?

[lock]

This thread has been automatically locked since there has not been
any recent activity after it was closed. Please open a new issue for
related bugs.

If you feel like there's important points made in this discussion,
please include those exceprts into that new issue.