> > 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 thread, you must ask the host application to > > provide a hook for Application.ProcessMessages (or equivalent if the host > > application is written using another language). You can do that by using a > > callback. > Hm, could that message pump be realised by a timer in the dll where the > application.processmessages is called each onTimer event? 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 message pump, or have you own thread with his own message queue and message pump (easier). -- [EMAIL PROTECTED] http://www.overbyte.be -- 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
