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)

"I cannot believe what a difference it makes trading with ProphetX!" - Comment from Bruce in Los Angeles

"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

"Can I get another account from you? I am tired of ******* going down so often" - Comment from George

"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

"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

"Previously I was using *******. IQFeed is WAY more economical, and for my charting needs is just as good, if not better." - Comment from Public Forum Post

"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

"I am very pleased with the DTNIQ system for quotes and news." - Comment from Larry

"Thanks for all of your help. Great customer service deserves to be recognized which one the reasons I've been a customer of DTN for over 10 years!" - Comment from Stuart

"I have to tell you though that using the IQFeed API is about the easiest and cleanest I have seen for some time." - Comment from Jim

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.