podman /libpod/v4/networks/json endpoint compatibility with v5 (v5+)?

[thediveo]

Take 2: I've noticed that my timing measurements of podman /libpod/v.../networks/json included the detection of the libpod API version using the /info endpoint. On reviewing my method I noticed this and commented out the API version detection. Now, performance figures for the networking API endpoints of Docker and Podman are en par:

• Docker: 631.226µs
• Podmen: 404.458µs and 320.279µs (with /_ping API detection: 494.475µs and 503.396µs)

On this basis, I've reworded my discussion title and question to how to properly deal with libpod API versioning? As I found out the hard way, the /info endpoint isn't the best for rapid API version detection...

What is the proper method I should use? Hardcode the /libpod/v4/networks/json? Would this also work with the upcoming podman 5 (5+) releases? At least based on the current planning and foreseeable future? Or always go through /_ping and then using the Libpod-Api-Version in a similar fashion to what the Docker client does?