+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-1109

Add a Connection event to IDataSource

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

Currently, the IDataSource events have no event to monitor for a disconnection of the data feed. Though the ITradingProfile does provide a Connection event, most brokers use a seperate order server and data server, meaning that a loss to the data server can't be monitored.

Plus, since the broker and data feed doesn't need to be the same provider (like with the use of IQFeed), an event for the connection of the data source would be even more valuable.

For risk management it would be very valuable if the automated strategy can be notified that the data feed has stopped updating (while the broker connection is still active). That way, the automated strategy can take precautions so that, when the data feed connection is restored, the strategy won't "go crazy" triggering needless orders because of the data gap that has happened. Also the trader can then be notified through an alert, and switch to his or her back-up data feed if needed.

Steps to reproduce this issue

n/a; this is a feature request.

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
    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