You _always_ need a message pump. If the calling program doesn't provide
one, you must provide one and to have one without interfering with the
calling DLL it is better to have all you stuff in a thread. Consider a
thread as a program within a program.
If you don't want to have a
Hm, could that message pump be realised by a timer in the dll where the
application.processmessages is called each onTimer event?
You can not use a TTimer since that uses windows messages and thus
needs the message loop. But you can use the windows SetTimer API with
a callback. I use such a
Francois Piette schrieb:
Defenitely not. Depending on the network traffic, you could easily have
something like one thousand
messages per second in the queue. The message loop must run full speed.
As I said, you must either provide a callback to the DLL to call the
application's
