[Quickfix-developers] QuickFIX's threading model and multiplexing other sources of events

[K. F. <kfr...@gm...>]

Hello List!

What is QuickFIX's conceptual threading model?

In realistic applications it is often necessary to "multiplex" several
different sources of events" command-line input from a console,
mouse and keyboard events from a gui, commands coming in
over a proprietary socket connect, market data, and of course,
FIX message traffic.

What's the QuickFIX-approved way of handling this kind of common
challenge?

What guarantees does QuickFIX make about which thread or threads
will call the various callbacks (e.g., fromApp or onMessage)?

Are there some standard design approaches that people have found
work well and fit the "QuickFIX way" of doing things?


Thanks.


K. Frank