Hi. I recently was doing some testing of XML-RPC clients/servers via script, noticed some odd behavior, and had a couple questions regarding it.
Basically, whenever you make multiple XML-RPC requests to the same object, it appears that it only keeps the last request on the xmlrpc.secondlife.com frontend server, as if there was only one queue slot for any particular object channel. However, all requests do end up at the script, all with message_id = NULL_KEY. Thus, if I respond to the first request in a batch, the external server which issued the latest request gets the response from the first request, and all other requests time out with no response, even though the script does process and attempt to return them.
First, is this intended behavior? I deign to report it as a bug, since it appears to be by design (though I have no clue why).
Second, what is the rationale of putting a 3-second enforced delay on the llRemoteDataReply function? It can't possibly be used to spam anything, since you can ONLY reply to a previously-received request, and with the problem outlined above, means it exacerbates it that much more.