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

[Hei C. <str...@ya...>]

There are ThreadedSocket* vs Socket* classes.
The latter has a queue for sending messages (for initiators) or a queue for receiving messages.


________________________________
 From: K. Frank <kfr...@gm...>
To: Quickfix Developers List <qui...@li...> 
Sent: Thursday, January 31, 2013 7:02 PM
Subject: [Quickfix-developers] QuickFIX's threading model and multiplexing other sources of events
 
QuickFIX Documentation: http://www.quickfixengine.org/quickfix/doc/html/index.html
QuickFIX Support: http://www.quickfixengine.org/services.html

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

------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_jan
_______________________________________________
Quickfix-developers mailing list
Qui...@li...
https://lists.sourceforge.net/lists/listinfo/quickfix-developers