In a console application the best practice (not only for TWSocket) is to
create a hidden window and an associated message pump. For the rest your
application is only a message loop. The program itself you can do in a
separate object just as it is a forms application. No need to call
MessageLoop or any other sequentinonal thing.
Met vriendelijke groeten,
Op 28-07-15 om 18:05 schreef Paul Read - nSolve Ltd:
In a console app's thread, I make a valid connection, I call
SslWSocket->Send, followed by MessageLoop.
Once I receive OnDataSent message I call SslWSocket->PostQuitMessage();
And the data is sent and the control returns to the thread - perfect.
The second time I want to send data (without closing-reopening the
connection - which is not allowed by Apple) the MessageLoop
immediately returns as SetTerminated(TRUE) was called once the
MessageLoop was exited in the previous send.
*Question what is the correct way to use a SslWSocket to send data
over a continuously open connection?*
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be