Sometimes we have multithreaded scenarios and always the problem is in concurrently accessing the same resource in two threads or more. So, common solution is each resource has a lock synchronization object. But it's not good if resources to be managed are many. How about safe resource manager from threads?
CObjBroker is manager class to distribute limited resources to threads. Surely
CObjBro have to be thread-safe. (and I hope it is) See below:
In demo, there are two resources called 'bro1' and 'bro2' who is poor programmer ( it's me.. ) and a third thread called 'project manager' who wants to get 'bro'. 'pm1' and 'pm2 get 'bro', and keep 'bro' working until 'bro' is tired. If 'bro' is tired then release 'bro'. Last, 3rd 'pm' is good 'pm'. He gets 'bro', then he lets 'bro' rest. If 'bro' is afresh, then release for other worker 'pm's.
CBroBroker is driven from
CObjBroker. And he manages 'bro's with
std::list. Demo code is easy to read, so you can get an idea from
I hope it helps you too. And I want your good advice and suggestion!