slowing down requests to evaalapi

[Francesco Potortì]

Dear competitors,

some of you reported that the server sometimes reports a 403 error,
because it can't keep up with the requests.  As a solution to this
problem, I can give two advices:

1. in the production version of your code, make the minimum number of
   requests possible, that is, only /nexdata; use /state requests only
   for development, you will find all the timing information in the log
   file anyway

2. wait for some time (for example 2s) after receiving a response before
   making a new /nexdata request

Please keep us updated on possible problems by writing to
info at evaal.aaloa.org

-- 
Francesco Potortì (ricercatore)        Voice:  +39.050.621.3058
ISTI - Area della ricerca CNR          Mobile: +39.348.8283.107
via G. Moruzzi 1, I-56124 Pisa         Skype:  wnlabisti
(gate 20, 1st floor, room C71)         Web:    http://fly.isti.cnr.it