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 started a trial a few weeks back before the market went wild. DTN.IQ didn’t miss anything and beat my other provider. I decided to stay with you because of the great service through all the volatility." - Comment from Mike
"IQ feed is brilliant. The support is mind-bending. What service!" - Comment from Public Forum Post
"You have an excellent feed. Very few spikes for Spot Forex." - Comment from Public Forum Post
"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
"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
"Thanks for following up with me. You guys do a great job in tech support." - Comment from Phelps
"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
"With HUGE volume on AAPL and RIMM for 2 days, everyone in a trading room was whining about freezes, crashes and lag with *******, RealTick, TS and Cyber. InvestorRT with IQFeed was rock solid. I mean SOLID!" - Comment from Public IRC Chat
"I used to have *******, but they are way more money for the same thing. I have had no probs with data from DTN since switching over." - Comment from Public Forum Post
"Just a quick one to say I'm very impressed so far :) The documentation for developers is excellent and I've quickly managed to get an app written to do historical downloads. The system is very robust and pretty quick considering the extent of data that's available. The support guys have been very helpful too, in combination with the forums it's been plain sailing so far!" - Comment from Adam
Home  Search  Register  Login  Blogs Recent Posts

Information on DTN's Industries:
DTN Oil & Gas | DTN Trading | DTN Agriculture | DTN Weather
Follow DTN_IQFeed on Twitter
DTN.IQ/IQFeed on Twitter
DTN News and Analysis on Twitter
»Forums Index »IQFeed Developer »IQFeed Developer Wish List »Echo original request with response
Author Topic: Echo original request with response (1 messages, Page 1 of 1)

EspressoE
-Interested User-
Posts: 30
Joined: Mar 8, 2006


Posted: Mar 16, 2006 11:58 PM          Msg. 1 of 1
This may apply to more than the history requests, but that's where I've run into this problem first.

When requesting history data, I will often process a batch of files to back-fill data. To speed up this process, I keep the socket open and go through a lot of request data, read response sequences. If something goofy happens (like getting two !ENDMSG! tokens for one request), it is possible for my software to read the first !ENDMSG! token and think that it's done. The next request would be made and then the second !ENDMSG! would be read and mistakenly matched up with the second request. (Note that the double !ENDMSG! problem is already scheduled to be fixed, but I feel there is still a need for a beginning-of-response token).

There are many ways to solve this, but I feel the most robust way would be to echo the original request back as the start of the requested data. Another possibility would be to add an additional field to the original request that will be passed back at the beginning of the data transmission. That would make it possible to be backwards compatible with the current implementation.

Current Implementation

TX> HD,[Symbol],[Days];
RX> Time Stamp, High, Low, Open, Close, Volume, OpenInterest<CR><LF>
. . .
RX> Time Stamp, High, Low, Open, Close, Volume, OpenInterest<CR><LF>
<CR><LF>!ENDMSG!<CR><LF>


Proposed Implementation with user-defined request sequence field. If the Request Sequence field is not provided, then the current functionality remains.

TX> HD,MSFT,10,[Request-Sequence];
RX> !BEGIN_MSG! Request Sequence<CR><LF>
RX> Time Stamp, High, Low, Open, Close, Volume, OpenInterest<CR><LF>
. . .
RX> Time Stamp, High, Low, Open, Close, Volume, OpenInterest<CR><LF>
<CR><LF>!ENDMSG!<CR><LF>



If this isn't clear, let me know and I'll try to explain some more...

P.S. This is similar in concept to the thread http://forums.iqfeed.net/index.cfm?page=topic&topicID=830

Edited by EspressoE on Mar 17, 2006 at 01:48 PM
 

 

Time: Sun January 20, 2019 3:44 AM CFBB v1.2.0 0 ms.
© AderSoftware 2002-2003