Do I need one or multiple FIX::Application instances for two way communications?

[Robert Levas]

Some parts of this message have been removed. Learn more about Nabble's security policy.

QuickFIX Documentation: http://www.quickfixengine.org/quickfix/doc/html/index.html
QuickFIX Support: http://www.quickfixengine.org/services.html

The docs are unclear about this, so I am posting my question to the list.

 

I am working on a solution where my application is to communicate with a FIX server and my application is supposed to send and receive FIX messages. I believe the FIX protocol is asynchronous and therefore a FIX::Application implementation that is configured to be an initiator can only send messages and is not set up to receive messages. So I need to also run a FIX::Application implementation that is configured to be an acceptor. 

 

Is this correct?  If so, is there any reason why I can’t have a single application instantiate multiple FIX::Application instances (one initiator and one acceptor)?

 

Thanks,

Robert Levas

Systems Architect/Developer

QED Financial Systems, Inc.

10,000 Sagemore
Marlton, New Jersey 08053 USA

tel       [phone]

fax      [phone]

email   levas@...

This electronic message is intended only for the receipt by, and the personal and confidential use of, the designated recipient(s) named
above.  If you are not an intended recipient of this electronic message you are hereby notified that any review, dissemination, distribution
or copy of this message is strictly prohibited.  QED Financial Systems, Inc. reserves all rights to the content of this electronic message, 
which is the exclusive property of QED Financial Systems.

 

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Quickfix-developers mailing list
Quickfix-developers@...
https://lists.sourceforge.net/lists/listinfo/quickfix-developers

[Grant Birchmeier]

QuickFIX Documentation: http://www.quickfixengine.org/quickfix/doc/html/index.html
QuickFIX Support: http://www.quickfixengine.org/services.html

The "initiator" and "acceptor" roles simply determine who is
connecting and who is waiting for a connection.  Otherwise, they are
not that different.  Both can do two-way communication.

It really sounds like you should poke through some of the example
programs before proceding further with your investigation.

-Grant


On Tue, Nov 3, 2009 at 1:14 PM, Robert Levas
<levas@...> wrote:

> QuickFIX Documentation: http://www.quickfixengine.org/quickfix/doc/html/index.html
> QuickFIX Support: http://www.quickfixengine.org/services.html
>
>
> The docs are unclear about this, so I am posting my question to the list.
>
>
>
> I am working on a solution where my application is to communicate with a FIX server and my application is supposed to send and receive FIX messages. I believe the FIX protocol is asynchronous and therefore a FIX::Application implementation that is configured to be an initiator can only send messages and is not set up to receive messages. So I need to also run a FIX::Application implementation that is configured to be an acceptor.
>
>
>
> Is this correct?  If so, is there any reason why I can’t have a single application instantiate multiple FIX::Application instances (one initiator and one acceptor)?
>
>
>
> Thanks,
>
> Robert Levas
>
> Systems Architect/Developer
>
> QED Financial Systems, Inc.
>
> 10,000 Sagemore
> Marlton, New Jersey 08053 USA
>
> tel       [phone]
>
> fax      [phone]
>
> email   levas@...
>
> This electronic message is intended only for the receipt by, and the personal and confidential use of, the designated recipient(s) named
> above.  If you are not an intended recipient of this electronic message you are hereby notified that any review, dissemination, distribution
> or copy of this message is strictly prohibited.  QED Financial Systems, Inc. reserves all rights to the content of this electronic message,
> which is the exclusive property of QED Financial Systems.
>
>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> Quickfix-developers mailing list
> Quickfix-developers@...
> https://lists.sourceforge.net/lists/listinfo/quickfix-developers
>

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Quickfix-developers mailing list
Quickfix-developers@...
https://lists.sourceforge.net/lists/listinfo/quickfix-developers

[Mikhail Veygman]

QuickFIX Documentation: http://www.quickfixengine.org/quickfix/doc/html/index.html
QuickFIX Support: http://www.quickfixengine.org/services.html

You misunderstand:

Think of Initiator as a socket that initiates the connection and
Acceptor as a socket that listens for a connection.

The communication through either is bi-directional, so in general you
will only need 1 implementation of FIX::Application per Initiator or
Acceptor whichever one you choose to implement.

FIX::Application is a base class that allows you to put in logic for
processing messages you receive.  You will need some other class to
generate and send messages via FIX.
-  
Regards,

Mikhail Veygman


-----Original Message-----
From: Robert Levas <levas@...>
Reply-to: levas@...
To: quickfix-developers@...
Subject: [Quickfix-developers] Do I need one or multiple
FIX::Application instances for two way communications?
Date: Tue, 3 Nov 2009 13:14:15 -0500

QuickFIX Documentation: http://www.quickfixengine.org/quickfix/doc/html/index.html
QuickFIX Support: http://www.quickfixengine.org/services.html

The docs are unclear about this, so I am posting my question to the
list.

 

I am working on a solution where my application is to communicate with a
FIX server and my application is supposed to send and receive FIX
messages. I believe the FIX protocol is asynchronous and therefore a
FIX::Application implementation that is configured to be an initiator
can only send messages and is not set up to receive messages. So I need
to also run a FIX::Application implementation that is configured to be
an acceptor.  

 

Is this correct?  If so, is there any reason why I can’t have a single
application instantiate multiple FIX::Application instances (one
initiator and one acceptor)?

 

Thanks,

Robert Levas

Systems Architect/Developer

QED Financial Systems, Inc.

10,000 Sagemore
Marlton, New Jersey 08053 USA

tel      [phone]

fax     [phone]

email   levas@...

This electronic message is intended only for the receipt by, and the
personal and confidential use of, the designated recipient(s) named
above.  If you are not an intended recipient of this electronic message
you are hereby notified that any review, dissemination, distribution
or copy of this message is strictly prohibited.  QED Financial Systems,
Inc. reserves all rights to the content of this electronic message,  
which is the exclusive property of QED Financial Systems.

 


------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________ Quickfix-developers mailing list Quickfix-developers@... https://lists.sourceforge.net/lists/listinfo/quickfix-developers


------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Quickfix-developers mailing list
Quickfix-developers@...
https://lists.sourceforge.net/lists/listinfo/quickfix-developers

[Robert Levas]

QuickFIX Documentation: http://www.quickfixengine.org/quickfix/doc/html/index.html
QuickFIX Support: http://www.quickfixengine.org/services.html


One again thanks for the info.... it was unclear from the docs that this is the way it worked.  I assumed that to receive messages that are not initiated by some previous request a second listener channel needed to be opened up.  

Thanks for the clarification.

Rob


-----Original Message-----
From: Mikhail Veygman [mailto:mveygman@...]
Sent: Tuesday, November 03, 2009 1:26 PM
To: levas@...
Cc: quickfix-developers@...
Subject: Re: [Quickfix-developers] Do I need one or multiple FIX::Application instances for two way communications?

You misunderstand:

Think of Initiator as a socket that initiates the connection and
Acceptor as a socket that listens for a connection.

The communication through either is bi-directional, so in general you
will only need 1 implementation of FIX::Application per Initiator or
Acceptor whichever one you choose to implement.

FIX::Application is a base class that allows you to put in logic for
processing messages you receive.  You will need some other class to
generate and send messages via FIX.
-  
Regards,

Mikhail Veygman


-----Original Message-----
From: Robert Levas <levas@...>
Reply-to: levas@...
To: quickfix-developers@...
Subject: [Quickfix-developers] Do I need one or multiple
FIX::Application instances for two way communications?
Date: Tue, 3 Nov 2009 13:14:15 -0500

QuickFIX Documentation: http://www.quickfixengine.org/quickfix/doc/html/index.html
QuickFIX Support: http://www.quickfixengine.org/services.html

The docs are unclear about this, so I am posting my question to the
list.

 

I am working on a solution where my application is to communicate with a
FIX server and my application is supposed to send and receive FIX
messages. I believe the FIX protocol is asynchronous and therefore a
FIX::Application implementation that is configured to be an initiator
can only send messages and is not set up to receive messages. So I need
to also run a FIX::Application implementation that is configured to be
an acceptor.  

 

Is this correct?  If so, is there any reason why I cant have a single
application instantiate multiple FIX::Application instances (one
initiator and one acceptor)?

 

Thanks,

Robert Levas

Systems Architect/Developer

QED Financial Systems, Inc.

10,000 Sagemore
Marlton, New Jersey 08053 USA

tel      [phone]

fax     [phone]

email   levas@...

This electronic message is intended only for the receipt by, and the
personal and confidential use of, the designated recipient(s) named
above.  If you are not an intended recipient of this electronic message
you are hereby notified that any review, dissemination, distribution
or copy of this message is strictly prohibited.  QED Financial Systems,
Inc. reserves all rights to the content of this electronic message,  
which is the exclusive property of QED Financial Systems.

 


------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________ Quickfix-developers mailing list Quickfix-developers@... https://lists.sourceforge.net/lists/listinfo/quickfix-developers



------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Quickfix-developers mailing list
Quickfix-developers@...
https://lists.sourceforge.net/lists/listinfo/quickfix-developers