KryoNet VS OkHttp

I am not sure if ppl would like to play with each other if they have to connect their phones directly (without using Bluetooth), but you can use the kryonet (https://github.com/EsotericSoftware/kryonet) for example (or any other java tcp server like netty) - it won't matter if it's ios or android.

I've taken a look at Kryonet and Netty, but they seem to only be for client-to-server models (Correct me if I'm wrong).

You really shouldn’t be sending complete classes over in general though, the server doesn’t need to know anything about rendering and only needs a data representation of it. You could have smaller packets that hold necessary information that you can pass between client/server and a common Network class that handles registering any objects you’ll be serializing! I believe the kryonet project has examples of this

If you are concerned with having to do a lot of implementation work yourself with Netty, then look no further than Kryonet.

There is kryonet: https://github.com/EsotericSoftware/kryonet

We will use Square’s Mock Webserver to spin up a mock server which we can use to simulate real api's request to the get coffee endpoint.

OkHttp Documentation

mockwebserver -> https://github.com/square/okhttp/tree/master/mockwebserver

I searched in the OkHttp GitHub project for an advice on which values may be suitable for Android apps nowadays but found no answers (only this old issue which does not help). Since we share a single OkHttp client Singleton for all our retrofit APIs and even Coil, I wonder if the default 5 maxRequestsPerHost is really enough.

You can technically add a Content-Length header for each part. It's not forbidden by the RFC, but nor is it common. It caused [problems](https://github.com/square/okhttp/issues/2138) for OkHttp, and they eventually removed it. Might be fine for internal-only use, though.

Boundaries are a lot like UUIDs, and rely on the same logic. When generating random data, once you have enough bits, the odds are against that sequence of bits ever having been generated before in the universe.

Lets be specific. This is the gradle build file for Squares okhttp client library. How exactly would your bld tool "predict" or "help" with all the parameters needed? There is no need to be defensive. Replace those large build files with your own, show where your approach is better and then understanding will lead to better solutions.

And adding to that: The asynchttpclient library is just a thin wrapper around OkHttp3, so it might be easier to just go with that instead: https://square.github.io/okhttp/

Retrofit in combination with OkHttp for fetching data from server (which hopefully already exists)

OkHttp