short version:
is it permissible to send off a whole series of request()'s in rapid succession?
(i’m not worried about the time it would take to get the responses - mainly just want to get everything shipped off to the server as fast as possible, before a flaky network connection fails, for instance)
thx
longer version (if needed):
say you have an “endless” game, with achievements for every N thingies overcome (each 1000 meters run, each 10 waves of aliens beaten, each 5 floors of jumping, whatever, doesn’t matter)
say a brand new player, on their first game, passes 3 “thingies”. by rights the following request should be made:
setHighScore 12345
unlockAchievement FirstThingyID
unlockAchievement SecondThingyID
unlockAchievement ThirdThingyID
can i just issue them all in sequence? or must I queue them, send first, await listener, get next off queue, send… repeat til done? any danger of “overloading” it internally, or will it handle immediately sequential requests gracefully?
(I’m asking about it’s internal design: built for it or not? not simply whether it just happens to work by coincidence once or twice - cuz it does seem to handle it, but I could just be lucky, on a fast connection that might just not “stress” it enough to expose a potential problem)