Hello,
Thanks for the insanely fast reply, I truly appreciate it!
All the code in my threads Execute method was uncommented once (I just commented them out when they did not bring the desired result) so my message pump was indeed in place.
The only thing I did not consider is that the component is taking the caller thread as it's parent, and not where it is actually located! When I create the component in Execute it starts to work!!! Thank you very much, I would have never guessed this.
Due to the nature of how I see code - is there a way to keep the creation in the OnCreate, and destriction in the Destroy method of the thread? I do not wish to create and assign a Client thread to each connection (Win2000 and Win2003 has really bad thread handling and I would like to stay compatible!) and a simple myhttpsrv.ThreadAttach in the beginning of the Execute does not bring joy.
If not - I'll just stick to this solution.
Thank you again!