+1 888 340 6572
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-1877

Concept of symbol matching in Charts, DOM .... Brokerfeed vs Datafeed

action_vote_minus_faded.png
3
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

The whole concept of symbol matching is a very good thing in MC.
BUT, it should be done properly, like SierraChart is doing it.

Here the classic example:
IB is not a good datafeed, while IQfeed is a very good one.

So far I am forced to use the "bad" IB feed and pay exchanges fees to IB for the "bad" feed to be able to place orders in MC-DOM window. Also I am paying once again fees to IQfeed for their good datafeed (which is of course fine).

The whole concept should be done like Sierracharts is doing it:

You should be able to choose your best datafeed (could be datafeed or brokerfeed to use MC terms) you want to use as the basis for all your trading decissions, i would like to call it MAINfeed.

Then you choose your brokerfeed, which is only the account you want to trade into it.
The brokerfeed does not need to subscribe again to a datafeed. So this avoids paying twice for the same data.

This way you pay only the exchange fees and datafees for the "best" datafeed you have choosen for your whole trading and use the broker only for your execution based on the MAINfeed.

The DOM and CHART TRADING should be fully based on MAINfeed. This allows to use level2 data from IQfeed and all the other good datavendors. They offer more level2 levels then IB is doing (IB has only 5 DOM levels, while others have 10 or more).
So here again another huge advantage.

Steps to reproduce this issue
Comments (0)
There are no comments
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
    Critical
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