Re: [Quickfix-developers] Design question: creating several SocketAcceptor/Initiator

[Oren M. <or...@qu...>]

Yoav, this is a reasonable thing to do. It just means that you will  
need a configuration file for each host.  If that is acceptable then  
you can set your system up this way no problem.

--oren

On Oct 26, 2007, at 5:08 PM, Yoav wrote:

> QuickFIX Documentation: http://www.quickfixengine.org/quickfix/doc/ 
> html/index.html
> QuickFIX Support: http://www.quickfixengine.org/services.html
>
> Hi,
> My company is developing a FOREX trading system and will most  
> likely use QuickFIX for the FIX implementation component.
> I'm new to QuickFIX and one of the first questions that just rose  
> was this:
> I can see that one SocketAcceptor/Initiator instance can handle  
> many connections to different hosts.
> The direction in my company though is to have one instance of  
> SocketAcceptor/Initiator per host.
> That means the same process that handles connections to many hosts  
> will have many instances of the class.
> Is that a reasonable decision? Is there a reason why we shouldn't  
> do that?
> I'm mostly interested in the performance aspect of this decision.
>
> Thanks in advance,
> Yoav
>
>
>
>
>
>
> ---------------------------------------------------------------------- 
> ---
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a  
> browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Quickfix-developers mailing list
> Qui...@li...
> https://lists.sourceforge.net/lists/listinfo/quickfix-developers
>