Hi all- As many know, I've been working to remove glib as a compilation dependency for non-tizen systems. I've done this in review 747: https://gerrit.iotivity.org/gerrit/#/c/747
My concern is with my threadpool implementation. The implementation in 747 is merely a dispatcher, starting and detaching a thread when requested. After analyzing the code, it seems like this should be sufficient, however a few comments have been made on the review that disagree. I wanted to extract that conversation here for further discussion. Another alternative that I thought of based on Ashok's feedback is an unlimited pool-thread system (essentially functionally like the glib implementation, since the thread_count is greater than requested threads), where the threads list is stored in an array list, then can be joined at the end. I'm not sure what that buys us other than blocking until all threads have been completed, but Ashok's comments seem to believe that it is a necessity. So, thoughts/comments? -Erich
