Hello Stanislav, > not possible to set the first socket in the "wait" state
Pause / Resume switch on / off a wait state. --- Rgds, Wilfried http://www.mestdagh.biz Wednesday, July 6, 2005, 12:29, Stanislav Korotky wrote: > Hello, All! > Thank you, Wilfried and Arno, for answering. I suppose I must > clarify the problem. Actually, I've already made a threaded > realisation of the thing I wanted, but from the theoretical > point of view I'm still curious to know what is a proper way > of doing this without threads. > Suppose we have an application which use sockets. All sockets > are created in the main (yet the single) thread and feeded by > the main message loop. Now suppose some socket need to send > a data which is partially related with another data to be received > from another socket, which, in turn, does not yet have the required > data. While we feed both sockets in the same message loop it is > not possible to set the first socket in the "wait" state, so to > speak, because we will not ever receive the awaited data. > The threaded approach is a decision. But I though of another one. > We could somehow filter socket messages in the message loop in > the way we need. The only question is what window property to > use for the filtering feature. Perhaps this could be a parent > window, but TWSocket windows are created without a parent, so > the changes should be made to the module anyway. > What do you think? Am I right, or do I just delude myself? > Best wishes, > Stanislav Korotky, > Russia, Moscow, CET +02:00 >>I'm not sure I understeand what you wants to do. TWSocket is event >>driven, so what is the reason you want to customize the window class ? > ... -- 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
