MAXCONNECTS is a noop since curl handles are thread local

[ligix]

Is your feature request related to a provblem? Please describe.
Setting MAXCONNECTS is a noop since the connection limit is per curl handle and handles are, by default, thread local which means that even if you use the same curl Session() you end up not reusing connections (or, at least, not more than one).

The only way setting that option may make sense is if you use AsyncSession.

Describe the solution you'd like
Provide a warning to the user if such a useless option is provided

Describe alternatives you've considered
Not provide a warning which I'm not convinced is any worse than providing one.

Additional context
More than a feature request I'm opening this to bring you this ""weird"" behavior to your attention in case you want to consider adding a runtime / documentation warning.

[ligix]

I've realized I don't care

[lexiforest]

This seems to be a real issue, why closing it?

[ligix]

Because I’m not sure what a proper fix would be, a runtime warning would be nice, but it would require maintaining a blacklist of known bad settings. On the other hand, a note in the documentation could also be helpful. At the end of the day, the requirements needed to trigger this are quite specific, and if you do actually encounter them, you are probably better off opening Wireshark and doing a surface-level pass through curl_cffi’s code to fully understand how you should use it.