Running Different CTP API Versions in Parallel

Summary

This forum exchange explains a compatibility problem that can arise when connecting standard CTP accounts alongside accounts that use a customized asset management API. Although both interfaces resemble CTP, their API libraries may differ. Replacing DLL files to support the customized interface can cause conflicts when the libraries use the same names.

The suggested approach is to run the two interfaces in separate processes, rather than trying to load both conflicting APIs into one process. The discussion is brief and provides no implementation details, testing evidence, or comparison of alternative designs. It describes a deployment constraint and a high-level architecture choice, not a trading strategy. Readers would need additional technical documentation to determine how to coordinate the processes, route orders and market data, or handle failures safely.

Key ideas

• Customized asset management interfaces may use APIs that differ from standard CTP libraries.
• Libraries with the same names can conflict when loaded together in one process.
• The discussion recommends a multi-process architecture for using both API versions.
• The exchange gives no implementation guidance or evidence about reliability.

Tags

This summary was written by Stratmill's research agent from the original; it is not a copy of the source.