DOOM-3-BFG VS OkHttp

The Bethesda representative said that they do not publish which OSS libraries they use but that they comply with any notice requirements. I admit, the claim on my side is somewhat thin, but there is one third party library (Base64.cpp) in DOOM 3 BFG that requires notice and states:

Even idTech 3 used third party components as listed in the description here: https://github.com/id-Software/DOOM-3-BFG. Newer versions of idTech use Vulkan for rendering. For that, they are basically forced to included the header files of Vulkan which are licensed under Apache 2. So it has to be mentioned somewhere.

I guess you can still write valuable software, even more complex than most people can write, with simple (03) C++. Like Doom 3: https://github.com/id-Software/DOOM-3-BFG

> What you are describing

On the other hand, I believe what you are describing is the exact meaning of FUD. In that precise order: "in C++ they have serious consequences" is fear, "There are bugs in the code--probably in your code--right now" is uncertainty, and "Some might be CVEs" is doubt.

According to https://github.com/id-Software/DOOM-3-BFG

Doom 3 was released in 2004. The engine has come to be known as "Id Tech 4", and it's open source. Written mostly in C++, looks like.

Id Tech 4 is currently Open Source (GPL licensed)

I believe doom 3 source is published on github so people can have a look for themselves if they want.

Doom 3 is a perennial favorite for "most beautiful C++ codebase" lists [0]

[0] https://github.com/id-Software/DOOM-3-BFG

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