Join the 80,000 other DTN customers who enjoy the fastest, most reliable data available. There is no better value than DTN!

(Move your cursor to this area to pause scrolling)




"I would just like to say that IQFeed version 4 is running very well and I am very happy with its performance. I would also like to extend a big thanks for the fast and efficient help that I always receive. My questions and concerns are always addressed promptly. Way to go!" - Comment from Josh in CO.
"This beats the pants off CQG, I am definitely switching to the ProphetX 3.0!" - Comment from Stephen
"If you are serious about your trading I would not rely on IB data for serious daytrading. Took me a while to justify the cost of IQ Feed and in the end, it's just a 2 point stop on ES. Better safe than sorry" - Comment from Public Forum
"I ran your IQFeed DDE vs. my broker vs. a level II window for some slow-moving options. I would see the level II quote change, then your feed update instantaneously. My broker's DDE, however, would take as much as 30 seconds to update. I am not chasing milliseconds, but half a minute is unacceptable." - Comment from Rob
"Thanks for the great product and support. During this week of high volume trading, my QuoteTracker + IQ Feed setup never missed a beat. Also, thanks for your swiftness in responding to data issues. I was on ******* for a few years before I made the switch over early this year, and wish I had done it a long time ago." - Comment from Ken
"Everything is working amazing now. I'm already impressed with the true-tick feed of IQFeed and it's ability to support my 480 symbol layout." - Comment from Tyler via Email
"I "bracket trade" all major news releases and I have not found one lag or glitch with DTN.IQ feed. I am very comfortable with their feed under all typical news conditions (Fed releases, employment numbers, etc)." - Comment from Public Forum
"Everything is working great ! Very impressive client. The news refreshes better and is more pertinent than the ******* feed I paid $ 100/month for. I Also like the charts a lot." - Comment from Leon
"Interactive Brokers tick data was inconsistent, so I have switched to using DTN exclusively. It is great to no longer have to worry about my datafeed all day long." - Comment from Philippe
"This is an excellent value, the system is generous (allowing for 500 stocks) and stable (and really is tick-by-tick), and the support is fantastic." - Comment from Shirin via Email
Home  Search  Register  Login  Recent Posts

Information on DTN's Industries:
DTN Oil & Gas | DTN Trading | DTN Agriculture | DTN Weather
Follow DTNMarkets on Twitter
DTN.IQ/IQFeed on Twitter
DTN News and Analysis on Twitter
»Forums Index »IQFeed Developer »IQFeed Developer Support »Questions on upgrading to protocol 6.0
Author Topic: Questions on upgrading to protocol 6.0 (5 messages, Page 1 of 1)

jonnyb
-DTN Evangelist-
Posts: 116
Joined: Aug 15, 2012


Posted: Jun 21, 2018 07:28 PM          Msg. 1 of 5
If I update the iqfeed client to 6.0.0.4 and keep all of my existing code running on protocol 5.2 nothing should break, is that correct?

Curious why LabelAtBeginning became the default option for historical interval data? Seems like leaving LabelAtEnd as the default would have been less disruptive and prevented the need for digging through old code to add a field.

Craig
-DTN Guru-
Posts: 250
Joined: Apr 16, 2010


Posted: Jun 22, 2018 04:58 PM          Msg. 2 of 5
I'd like an answer regarding the interval changes as well, why?

DTN_Tim Walter
-DTN Guru-
Posts: 1238
Joined: Apr 25, 2006


Posted: Jun 23, 2018 05:07 PM          Msg. 3 of 5
Hello,

This change was to bring us in line with what it felt like new developers were expecting from us. Many competitors do not provide an option of how to label their intervals and when comparisons were being done, there would invariably be off by one problems. This was to help eliminate that hurdle.

We felt that, since this would not affect any past protocols, that we could add this change without impacting users much. My expectation was that if someone was going to be editing their code anyhow, to update the protocol, then adding the additional parameter to the HIT, HIX, and HID requests would be acceptable.

My apologies if I underestimated that.

Tim

altmany
-Interested User-
Posts: 45
Joined: Jul 30, 2018

IQML - IQFeed-MATLAB connector


Posted: Jul 30, 2018 05:56 AM          Msg. 4 of 5
Perhaps the transition to 6.0 could be made easier if there were a global option that could be set during connection time and would apply a default value to LabelAtBeginning for all subsequent historic data requests (similar to setting the CLIENT NAME). Then users could set that option directly adjacent to the code that sets the protocol, and would not have to worry about modifying any of the data queries elsewhere in their program. Perhaps something such as this:

S,SET OPTION,DefaultLabelAtBeginning,0

Then, if the users use the standard HIX/HID/HIT commands without the extra LabelAtBeginning field (as in legacy 5.0-5.2 code), the new DefaultLabelAtBeginning would apply, and if they do specify the field then it would take precedence.

You can easily extend this mechanism to other options in the future.


- Yair
IQML - IQFeed-Matlab connector
https://undocumentedmatlab.com/IQML

Edited by altmany on Aug 2, 2018 at 04:41 AM

DTN_Tim Walter
-DTN Guru-
Posts: 1238
Joined: Apr 25, 2006


Posted: Jul 30, 2018 12:12 PM          Msg. 5 of 5
That is certainly fair, that would also be useful for setting protocols and more.

We'll discuss it and see if it could be worked in sometime for a future release. Thanks for the idea.

Tim
 

 

Time: Mon March 30, 2020 12:24 PM CFBB v1.2.0 31 ms.
© AderSoftware 2002-2003