dis
-Interested User-
Posts: 24
Joined: Apr 16, 2007
|
Posted: Jun 4, 2007 10:23 AM
Msg. 1 of 6
Suggestion is following: Raise an event in case when no data available for the requested interval. Now my calling thread is sleeping up to timeout (20 seconds - 1 minute for me). It would be great if the event would inform about it immediately. It is very important for my application.
Many thanks for your consideration.
|
DTN_Steve_S
-DTN Guru-
Posts: 2096
Joined: Nov 21, 2005
|
Posted: Jun 4, 2007 10:28 AM
Msg. 2 of 6
Can you give me an example of the request you are making?
|
dis
-Interested User-
Posts: 24
Joined: Apr 16, 2007
|
Posted: Jun 8, 2007 07:07 AM
Msg. 3 of 6
HistoryLookupClass.RequestMinuteHistory("MSFT", 1, 1); The situation reproduces if I'm doing such request on Monday morning (or holidays...), because there is no historical data.
|
DTN_Steve_S
-DTN Guru-
Posts: 2096
Joined: Nov 21, 2005
|
Posted: Jun 8, 2007 09:31 AM
Msg. 4 of 6
What you are requesting is actually the intended functionality of IQFeed.
You are experiencing a bug that is specific to the HistoryLookup interface. It does not exist in the HistoryLookup2 interface or in the sockets interface.
|
dis
-Interested User-
Posts: 24
Joined: Apr 16, 2007
|
Posted: Jun 8, 2007 10:29 AM
Msg. 5 of 6
I'm not experiencing a bug, I'm offering you to enhance it a bit so that the AbortLoad event needs to be raised in some additional case, or MinuteProgress event brings 0 bars loaded in its event args in case if there is no data on the requested interval. This does not require the changes in the interface.
|
DTN_Steve_S
-DTN Guru-
Posts: 2096
Joined: Nov 21, 2005
|
Posted: Jun 8, 2007 10:38 AM
Msg. 6 of 6
I never said that it required changes to the interface. I simply said that this interface is the only interface affected.
The fact that the request takes a LONG time to return an error in the given scenario, IS the bug. It is due to a combonation of factors involving the communication with the servers. It will be fixed in an upcomming release of IQFeed.
|