Post by Petar PoparaP.S. I'm thinking of implementing some pool of SSL connections to the
server and each thread would take and give back thread when doesn't need
it any more. Does it have any sense? Is there some similar example?
http://www.codeproject.com/threads/cpthreadpool001.asp
I read a good answer on your question at MFC NG - the main idea is "it's not
enough to create a huge amount of threads, your application should have nice
design and implementation..."
So making a thread pool is good idea to avoid calling CreateThread each time
when you need to do something, but you should estimate, how much threads you
need, how much job should be performed, how much time threads might be idle.
I recommend you not create pool with 100 of threads instead make
estimations, draw the model in your head (or on the page) and then implement
it.
--
Vladimir