possible performance problems about kohttp

[rybalkinsd]

Thanks for posting this issue @alosdev!

Overall, It's a great idea to introduce a simplified API to work with response streaming.

Indeed, in the quoted file we load the whole response.
The main idea of .toType extension is to deserialise simple/small bodies as type T

val simple: SimpleClass? = it.toType()

In this case we have an extra allocation(for tmp string) + sequential processing vs streaming processing overhead.
In my mind it would be great to have a benchmark to make a decision.
Do you have any use case in your mind?

From my understanding getting deserialized type T or JsonNode itself will not radically change the situation (the whole object will be in memory after parsing)
However parsing arrays of to Stream<T> or fetching a particular filed(sub-object) from a huge body could help.
Do you have any thoughts about API?