Thread safety about liboparl

[grindhold]

konstin: the library emits the resolve_url signal everytime it needs something from teh interwebs. this lets you decide how to handle/queue/parallelize the upcoming requests in your application code. the parse methods (and thus writing operations) are called once per object. when you implement an OParl.Cache in your code, this can be regarded as guaranteed, so i think no additional locks are necessary.

[grindhold]

soooo. i now ran into (and immediately fixed) the first race condition problem.
i currently develop a threaded program against the lib, so this will be
tested as of now.
i am closing this issue as it is not an open question anymore. some work on
thread-safety has to happen.