
For further details on why I need this information see my comment at:
http://secondlife.com/badgeo/wakka.php?wakka=llHTTPRequest
As it stands I will be forced to do a bunch of time keeping and defensive programming to prevent a throttle (and potential loss of user input). Getting throttled would make it very difficult to prevent my scripts from getting locked into a state they can't get out of.
what I want to do is (pseudo code)
while (key != null) {
key = llHttpRequest(stuff)
if (key == null) { // <--- We got throttled!
sleep(throttleExpriationInterval);
}
}
Of course I can work around the unknown throttle time, but it all requires a more programming work for me, and more processing time for your servers. I could also spend some time in the test sim and determine the time empirically, but then any undocumented changes could totally hoze me. Since player actions cause requests I can't control the rate of requests directly. As it stands I can't even tell the user try again in X seconds cause I don't know what X is.
I expect throttling to be a rare case, but an important one for me to handle correctly. I'm not building anything that is likely to generate frequent throttles, just something I don't want to die if it does happen.
Thanks,
Sai Harbinger
P.S. Other better solutions for future patches include an event that can be caught to detect the unthrottle conditions, and an option to opt for blocking calls that don't return until the the request has been sent (thereby handling a throttle automatically). Another posibility is a function that tests to see if a throttle will be imposed, and returns the time one must wait to avoid a throttle. Really just anything that lets my script know how to not cause problems gracefully. Obviously not all of those are needed, but at least one would be nice.