|
Exchange Street
Registered User
Join date: 6 Sep 2004
Posts: 69
|
11-04-2005 09:47
Because a number of SL-based businesses are using XML-RPC for transactional communications, it would be beneficial if a TTL flag was added to XML-RPC requests so truly fault-tolerant communications could be made into reality.
The implementation would be simple - existing XML-RPC communications would continue to work as-is with a 30- or 60-second default TTL. There could also be a TTL element in the XML request to specify a custom value.
On the scripting side, if the TTL expires before the event is fired in the LSL script, the event is cancelled and removed from the queue.
|
|
Iron Perth
Registered User
Join date: 9 Mar 2005
Posts: 802
|
11-04-2005 10:35
Are the servers synchronized via ntp? You could pass in the message construction time and implement ttl that way.
|
|
blaze Spinnaker
1/2 Serious
Join date: 12 Aug 2004
Posts: 5,898
|
11-04-2005 10:47
ugh, do you really want to trust SL so sync all the servers? better to have ttl implemented at one gateway.
of course, lets face it, LL is probably going to implement transactional functionality >in< SL before they support it happening outside of SL.
they want to be the the transaction db for everything, after all.
|
|
Exchange Street
Registered User
Join date: 6 Sep 2004
Posts: 69
|
11-14-2005 11:41
Bumping because this really is a necessary bugfix, er I mean enhancement. It is not reasonable for a client to have to wait 10 or more minutes for a reply when something goes wrong with a sim.
|