psl_latest() allocates memory, loads the appropriate file contents into that dynamic memory and returns a pointer to a new "context" that needs psl_free() to get freed after use.

We thus need to cache the loaded results somewhere for some amount of time after use to make this bearable and not cause too much of a performance impact. We can't make it globally cached without also making it not thread safe.

We can't make it globally cached without also making it not thread safe.

Does that mean we have to keep one PSL per handle ? Or would we introduce share interface options for it ?

Does that mean we have to keep one PSL per handle ?

Yes. But we can make the multi handle own it so that at least the use case with multiple transfers using the multi api will only use a single copy.

Or would we introduce share interface options for it ?

I think we should. I think it should be separate from the existing cookie sharing since the PSL is more likely to be the same for all transfers in an application.