Closed swankjesse closed 1 year ago
Do we have any indication of the % usage of OkHttp in
a) Android clients b) desktop/low volume clients c) servers/high volume clients
I've actually suggested some internal usage of c) look at other libraries (netty etc) because I don't have the same expectation that OkHttp will scale as well because of the threading model.
Yeah, I prefer small vs. scalable when the two are in conflict. For example, we don’t do any native code!
We can go toe-to-toe with Netty in all but the most extreme cases. We are very GC-friendly and small. And I also think OkHttp server is something we can do competitively if we get coroutines right.
I’m using kotlin coroutines extensively in my client so that’s awesome to hear even for client only use
Closing as a dupe of https://github.com/square/okhttp/issues/4530, a lot of overlap here.
It's been problematic in crawlers. https://github.com/apache/nutch/pull/328