Implications of Data Request limit

[chopper]

I'm not a programmer so I may be completely wrong in my thinking about how an application works with an API. Hopefully someone can understand what I'm getting at:

Assume I'm betting on a football match between Man U and Arsenal and my trading strategy is to trade both teams at the same time (or near in time as possible).

If I assume it takes 5 requests to check prices, my position etc and then given my conditions are met a 6th request to trade a certain stake of Man U and a 7th request to trade a certain stake of Arsenal. So a roundtrip to completing my trading strategy is 7 requests.

If I limit my requests to 20 a second. If at the start of the second I do two successful roundtrips that leaves me with 6 requests left. If the conditions are there that I want to complete another roundtrip then would I end up trading in Man U (on my 20th request) and therefore not trading in Arsenal and being left with an undesirable position?

Thanks

[GaryRussell]

Assuming you are referring to Betting Assistant and not an application using the free API.

1) Placing bets is not counted as a data request. You do have to be aware though that they charge 1 pence for each bet in excess of 1000 in each hour.

2) Betting Assistant does not ignore requests that would go over the throttle limit, it queues them so they will be sent in the next second.

[doris_day]

Why limit yourself to 20/sec ?

I never put a limit on my requests and except for a couple of occasions when I had a number of markets open at once, I've never had to pay for data.

Once upon a time I didn't care because data charges could be offset against my PC charges but eventhough that wrinkle has gone, if you trade in any reasonable size, your trading credits should easily cover any excess data requests.

To check you're not going wildly over your allowances simply go to 'Account' at the top of Gruss and scroll down to 'Calculate data requests allowed'.

Have fun...