MultiCharts Easter Sale has jumped in! Up to 50% off Explore offers
+1 888 340 6572 GET STARTED
MultiCharts Project Management
previous_open_issue.png
Go to the previous open issue
previous_issue.png
Go to the previous issue (open or closed)
star_faded.png
Please log in to bookmark issues
feature_request_small.png
Open Feature request MC-2133

generic fix engine for interaction with fix compliant brokers

action_vote_minus_faded.png
1
Votes
action_vote_plus_faded.png
next_issue.png
Go to the next issue (open or closed)
next_open_issue.png
Go to the next open issue
Description

Great feature ...
Matlab has it
R has it
Python has it and the list goes on ...
Broker Connections with 3rd parties that provide a FIX interface would then be possible.No more one broker per year integration and the likes ...

Steps to reproduce this issue

FR

Comments (1)
#1
user-offline.png  orad (orad)
May 13, 2017 - 03:01

Supporting Financial Information eXchange (FIX) will add a wide range of brokers to connect to MultiCharts. People usually find a broker first and then go for a trading platform. If the broker is not supported in a platform, they won't switch to a different broker, they will switch to a different platform. So it would be a very wise decision for TS Support to support FIX.

I even think maybe MC should, in addition to supporting FIX, provide a pluggable system so developers can create their own broker integrations for MultiCharts. MultiCharts .NET would be great for this. That will be very beneficial to both MC and the users.

History
Issue basics
  • Type of issue
    Feature request
  • Category
    Usability
  • Targeted for
    Not determined
  • Status
    Not Reviewed
User pain
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
Affected by this issue (2)
People involved
Times and dates
  • Posted at
  • Last updated
Issue details
  • Resolution
    Not determined
  • Severity
    Normal
Attachments (0)
There is nothing attached to this issue
Commits (0)
There are no code checkins for this issue
Duplicate issues (0)
This issue does not have any duplicates