General Betting
Welcome to Live View – Take the tour to learn more
Start Tour
There is currently 1 person viewing this thread.
Getting varying roundtrip times to getMarketPricesCompressed ... anything from 5+ per sec to 0 per sec.
Tried it on 2 different connections on that first race at Navan ... same problem with both
Is it just me?
Tried it on 2 different connections on that first race at Navan ... same problem with both
Is it just me?
Show More
it's getting worse here ... more or less stopped during the first at Kelso and second Navan Race
Yeah, it's in fairly poor shape. I'm getting old data returned just about every other call
There's an announcement up saying there's a problem with the Beta Site, but no mention of the api ....
is there a problem generally with internet? my o2 is playing up? could this be linked?
Hazel,
my 'Be' broadband is also playing up ( o2 is a white label of 'be' )
seems to be something to do with the DNS lookup server.
Loading any webpage is about 50/50 for me at the moment but my own API program is connecting to betfair OK.
my 'Be' broadband is also playing up ( o2 is a white label of 'be' )
seems to be something to do with the DNS lookup server.
Loading any webpage is about 50/50 for me at the moment but my own API program is connecting to betfair OK.
seems to have suddenly perked up ... storming along on the 14.40 Newbury ... weird.
speed is fine at mo for me, the BET_IN_PROGRESS aren't helping tho
it's going nuts here ... shows the market correctly for about 5 updates, then bounces back to the market 5 updates previously, then bounces back to current market ... just can't trust it, for the remaining races
Am I right in thinking that the APIResponseHeader's timestamp can be used to determine the age of the data returned?
I used to think that when old data was being returned, the header timestamp would still be up-to-date, but I've just had a look at some of the headers in my program running at the moment, and the timestamps appear to be out of date (in line with the out of date data).
Presuming this is so (that the timestamps will reveal the age of the data), it is obviously a simple matter to program an application so as to ignore this old data.
I used to think that when old data was being returned, the header timestamp would still be up-to-date, but I've just had a look at some of the headers in my program running at the moment, and the timestamps appear to be out of date (in line with the out of date data).
Presuming this is so (that the timestamps will reveal the age of the data), it is obviously a simple matter to program an application so as to ignore this old data.
good idea Contrarian, but I just checked the API manual, and under "APIResponseHeader" it says:
"timestamp: DateTime: This field is deprecated and it should not be relied on for determining the order or age of responses."
http://bdphelp.betfair.com/API6/6.0/RefGuide/wwhelp/wwhimpl/js/html/wwhelp.htm
of course it might be deprecated for the very reason that responses might not come in the 'correct' chronological order, so it would be ok to use it in one service, e.g. getMarketPricesCompressed to weed out rogue responses, but i couldn't be sure of that.
"timestamp: DateTime: This field is deprecated and it should not be relied on for determining the order or age of responses."
http://bdphelp.betfair.com/API6/6.0/RefGuide/wwhelp/wwhimpl/js/html/wwhelp.htm
of course it might be deprecated for the very reason that responses might not come in the 'correct' chronological order, so it would be ok to use it in one service, e.g. getMarketPricesCompressed to weed out rogue responses, but i couldn't be sure of that.
Post Your Reply
Please login to post a reply.
Wonder
Instance ID: 13539