DTN IQFeed, DTN.IQ, DTN ProphetX Support Forums

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)

"After all the anxiety I had with my previous data provider it is a relief not to have to worry about data speed and integrity." - Comment from Eamonn

"I am a hedge fund manager here. It’s funny, I have a Bloomberg terminal and a Bridge feed, but I still like having my DTN feed!" - Comment from Feras

"IQ feed works very well, does not have all of the normal interruptions I have grown used to on *******" - Comment from Mark

"I am very happy I changed. I love the product, but more so I am thrilled with Tech Support. You are knowledgeable, polite, pleasant and professional." - Comment from Pat

"Everything is working great with the API. I love it." - Comment from Calvin

"I am enjoying the feed very much - so superior to the broker provided feed I was previously using." - Comment from George

"I'm satisfied with IQFeed. It's the most reliable and fastest quote feed I have ever used. Although I'm a resident in China, it's still very fast!" - Comment from Xiaofei

"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

"I've been using IQFeed 4 in a multi-threaded situation for the last week or two on 2600 symbols or so with 100 simultaneous daily charts, and I have had 100% responsiveness." - Comment from Scott

"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

Home

Recent Posts

Information on DTN's Industries:
DTN Oil & Gas | DTN Trading | DTN Agriculture | DTN Weather

DTN.IQ/IQFeed on Twitter
DTN News and Analysis on Twitter

»Forums Index »Archive (2017 and earlier) »IQFeed Developer Support »[COM]: Daily and intraday history requests from separate threads

Author	Topic: [COM]: Daily and intraday history requests from separate threads (6 messages, Page 1 of 1)
dis -Interested User- Posts: 24 Joined: Apr 16, 2007	Posted: Jun 8, 2007 09:02 AM Msg. 1 of 6 Is it possible to do 2 historical requests (daily and intraday) from separate threads at the same time? Can the data be corrupted in such situation?
DTN_Steve_S -DTN Guru- Posts: 2093 Joined: Nov 21, 2005	Posted: Jun 8, 2007 09:08 AM Msg. 2 of 6 This is 100% possible. I know that several of our developers use the COM requests in this way. There should not be any chance of data corruption.
dis -Interested User- Posts: 24 Joined: Apr 16, 2007	Posted: Jun 8, 2007 09:37 AM Msg. 3 of 6 But... If OnAbortedLoad event would be raised, how I could determinate which request failed?
DTN_Steve_S -DTN Guru- Posts: 2093 Joined: Nov 21, 2005	Posted: Jun 8, 2007 09:45 AM Msg. 4 of 6 Since you would be using multiple threads, each request (and response) should be completely isolated from each other request. As a result, you would determine this the same way you do now with a single request.
simon33 -Interested User- Posts: 28 Joined: Apr 9, 2005	Posted: Jun 11, 2007 10:39 PM Msg. 5 of 6 However, this is not possible via TCP/IP correct? I have attempted this and it appears to handle them sequentially (I use java and connect via sockets). Does that match the information that you have? I ask because even though it seems to be sequential handling of requests (I turned on DTN logs and that is what I see) we did have a situation in our logs that seems to indicate otherwise.
DTN_Steve_S -DTN Guru- Posts: 2093 Joined: Nov 21, 2005	Posted: Jun 12, 2007 09:25 AM Msg. 6 of 6 TCP/IP handles it the same way as COM. If you make simultaneous connections, they will get executed simultaneously. Depending upon exactly how you are making your requests, the logs may not be a very good indicator of what is acutally happening. This is a design flaw of the logging implementation in IQConnect. If you open 2 separate socket connections to IQConnect and make simultaneous requests, you will get data returned on both sockets simultaneously. If you open a single socket and make 2 separate requests at the same time, they will be executed sequentially.