Is this lib thread-safe?

[Jason Yu]

The methods that I exactly mentioned are uriParseSingleUriA, uriDissectQueryMallocA, and uriFreeQueryListA.

[Sebastian Pipping]

I can think of two aspects to this question:

• Uriparser doesn't have global state, so you can e.g. parse URIs in multiple threads without conflict.
• Uriparser doesn't use any locks or other means of synchronization by itesel. Whenever another thread is writing to UriUri[AW] structures, no other thread should be writing or reading from it: the app using uriparser will have to use locks/mutexes/... itself.

Does that answer the question?

[Jason Yu]

I see, thanks!