Re: [Quickfix-developers] Configuration Failover Settings

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

John,

When you have multiple connection points that share the same comp id's, 
cycling through the connections is a necessity because you can't keep 
the same session alive simultaneously on multiple hosts/ports.  But if 
you failover sessions with unique compids and unique sets of sequence 
numbers, why would you not just keep these connections up at all times?

--oren

On Jun 9, 2004, at 10:46 AM, Jon Dahl wrote:

> QuickFIX Documentation: 
> http://www.quickfixengine.org/quickfix/doc/html/index.html
> QuickFIX FAQ: http://www.quickfixengine.org/quickfix/doc/html/FAQ.html
>
> I have been asked to research QuickFIX's scalability/failover 
> capabilities
> by our Ops center and have come upon an issue. I think I found a 
> situation
> where the clients won't be able to connect to an alternate gateway in 
> case
> of a failure.
>
> Let's say a client has two hosts(gateways) to connect to. Each one has 
> a
> separate SenderCompID. If the client detects a failure and tries to
> connect to the secondary host, it will fail to connect because its
> TargetCompID is for the primary host and not the secondary one.
>
> I was wondering if there was a way to have the [SESSION] settings have
> alternate TargetCompID's to go a long with SocketConnectPort[n] and
> SocketConnectHost[n]?
>
> JD
>
>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: GNOME Foundation
> Hackers Unite!  GUADEC: The world's #1 Open Source Desktop Event.
> GNOME Users and Developers European Conference, 28-30th June in Norway
> http://2004/guadec.org
> _______________________________________________
> Quickfix-developers mailing list
> Qui...@li...
> https://lists.sourceforge.net/lists/listinfo/quickfix-developers
>