On Sun, 06 Apr 2014 09:35:51 +0200, Sönke Ludwig wrote:
How bad was your experience with it in this case?
Not very bad. I expected something like that.
I develop quite a large application with heavy i/o to/from external web-services. And I need something like a Tasks queue. The order is not important, but no task should wait forever.
Now I use TaskMutex with yield() after unlocking, because there are no blocking operation between locking and unlocking the mutex. But I don't like this idea. As I understand a generic platform independent mutex doesn't guarantee any order of aquiring locks.
What would you recommend? Using TaskMutex or it may be better to write some Tasks queue?