Dan, I think you are overcomplicating things. What you are describing is easily achievable with a main processing thread, a synchronized queue, and a pool of worker thread(s). It also looks like you are falling into a common trap of using locks to "protect code", while it's the data structures you need to protect.
Dan, I think you are overcomplicating things. What you are describing is easily achievable with a main processing thread, a synchronized queue, and a pool of worker thread(s). It also looks like you are falling into a common trap of using locks to "protect code", while it's the data structures you need to protect.
Define your shared data, identify minimal critical sections when the data might be inconsistent. Brace that with locks.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.