Imported from previous forum
[ original email was from Nidhi Oberoi - nidhio@hotmail.com ]
Can one instance of FIX engine Installed on a server (be it javelin, cameron ,tradeware ,ttConnect )capable to support all FIX versions ?
If a Buy side client is on 4.1 and another Buyside client is on 4.2 …can they be connected to the same instance of SellSide FIX engine and this engine will be able to run both 4.1 and 4.2 fix sessions?
It is certainly possible to develop a FIX engine such that it supports different versions for different FIX sessions. I can’t speak for all of the vendors (hopefully they’ll respond to you directly vs. post/boast within this discussion forum), but I can say that we built our proprietary engine that way. I’m pretty sure most of the commercial engines support this via a configuration setting.
> Can one instance of FIX engine Installed on a server (be it javelin, cameron ,tradeware ,ttConnect )capable to support all FIX versions ?
> If a Buy side client is on 4.1 and another Buyside client is on 4.2 …can they be connected to the same instance of SellSide FIX engine and this engine will be able to run both 4.1 and 4.2 fix sessions?
>
While it is certainly possible to develop a FIX engine whose multiple instances can support different versions of the protocol according to their configuration files [I speak from experience having developed an in-house FIX engine and application translator], I know of no FIX engine that will support multiple protocol version numbers from the same instance. Even massively scalable servers will spawn a new thread or child process per FIX session initiated.
> It is certainly possible to develop a FIX engine such that it supports different versions for different FIX sessions. I can’t speak for all of the vendors (hopefully they’ll respond to you directly vs. post/boast within this discussion forum), but I can say that we built our proprietary engine that way. I’m pretty sure most of the commercial engines support this via a configuration setting.
>
>
> > Can one instance of FIX engine Installed on a server (be it javelin, cameron ,tradeware ,ttConnect )capable to support all FIX versions ?
> > If a Buy side client is on 4.1 and another Buyside client is on 4.2 …can they be connected to the same instance of SellSide FIX engine and this engine will be able to run both 4.1 and 4.2 fix sessions?
> >
>
Andrew, I understood the original question as "can I acquire/build one product/application which supports different FIX versions so that I can speak to counterpary A using FIX 4.0 and counterparty B using FIX 4.1, etc?" This is different from "can the same thread/child process instance of a product/application…".
> While it is certainly possible to develop a FIX engine whose multiple instances can support different versions of the protocol according to their configuration files [I speak from experience having developed an in-house FIX engine and application translator], I know of no FIX engine that will support multiple protocol version numbers from the same instance. Even massively scalable servers will spawn a new thread or child process per FIX session initiated.
>
> > It is certainly possible to develop a FIX engine such that it supports different versions for different FIX sessions. I can’t speak for all of the vendors (hopefully they’ll respond to you directly vs. post/boast within this discussion forum), but I can say that we built our proprietary engine that way. I’m pretty sure most of the commercial engines support this via a configuration setting.
> >
> >
> > > Can one instance of FIX engine Installed on a server (be it javelin, cameron ,tradeware ,ttConnect )capable to support all FIX versions ?
> > > If a Buy side client is on 4.1 and another Buyside client is on 4.2 …can they be connected to the same instance of SellSide FIX engine and this engine will be able to run both 4.1 and 4.2 fix sessions?
> > >
> >
>
[ original email was from Sam Johnson - sam.johnson@transacttools.net ]
the short and sweet answer is "yes". a number of commercially-available engines support simultaneous connections with different protocol versions.
keep in mind that message format and content varies among fix versions, so to support different versions simultaneously will require some level of translation/normalization.
there is significant variation among commercial engines as far as these capabilities go. if the necessary translation and normalization cannot be done easily inside the engine itself, it will have to be done externally, by you, in the business application.
happy to discuss this in more detail off-line if that’s helpful.
> Can one instance of FIX engine Installed on a server (be it javelin, cameron ,tradeware ,ttConnect )capable to support all FIX versions ?
> If a Buy side client is on 4.1 and another Buyside client is on 4.2 …can they be connected to the same instance of SellSide FIX engine and this engine will be able to run both 4.1 and 4.2 fix sessions?
>