Tweet
I am finding a disturbing large number of socket errors being reported (which in turn cause timeouts) from call to the new API.
These socket errors seem to suggest that the connection has been closed by the remote end.
Does the API-NG throttle access (i.e. it forcibly closes the connection if there are more than x requests in a second)?
My application is geared to send about 8 requests per second, but they are not necessarily evenly spread-out. So 8 requests could be fired in the first few milliseconds then no more requests for the rest of the second.
Is this an issue?
Do I need to spread out the calls so that one call is fired every x milliseconds?
I am finding the new API somewhat frustrating and these sorts of issues are just compounding things.
These socket errors seem to suggest that the connection has been closed by the remote end.
Does the API-NG throttle access (i.e. it forcibly closes the connection if there are more than x requests in a second)?
My application is geared to send about 8 requests per second, but they are not necessarily evenly spread-out. So 8 requests could be fired in the first few milliseconds then no more requests for the rest of the second.
Is this an issue?
Do I need to spread out the calls so that one call is fired every x milliseconds?
I am finding the new API somewhat frustrating and these sorts of issues are just compounding things.
Comment