Just  a  word to say I recently had that kind of 100% CPU problem in a
thread.  I  was  starting  a new project with different WSocket and as
always  I "prepare" all the OnXXXX events procedures I will need but I
forgot  to put a ReceiveStr in the one of the OnDataAvailable so after
receiving  first  data, the event from this Socket always fired up and
put 100% CPU.


To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be

Reply via email to