Tech Support > Microsoft Windows > Development Resources > socket communication blocks gui thread
socket communication blocks gui thread
Posted by Torsten Curdt on August 27th, 2003


I don't get this: in a worker thread I am doing socket
communications. For some reason this heavily influences
(almost blocks) the gui thread.

At least in the DEBUG version it's kinda like I have
to wait for the socket transfer is finished until
my dialog finally gets closed - although I've hit the
button seconds before.
I can move the dialog but closing takes ages.

AFAIU there should be no relation - different threads!
Did I miss something?
--
Torsten

PS: It's on WinCE4.2

Posted by Torsten Curdt on August 27th, 2003


Torsten Curdt wrote:
Maybe because I initialize WS with:

AfxSocketInit();
AfxEnableControlContainer();

....I only used the usual "recv" and "send" WS calls.
Maybe I should better use the usual WS way?

Any idea?


Posted by Serve La on August 27th, 2003



"Torsten Curdt" <tcurdt-REMOVE@web.de> wrote in message
news:bii4mp$9pge4$1@ID-37954.news.uni-berlin.de...
can't help, but maybe alt.winsock.programming is a better place for you?




Similar Posts