Open Morketh opened 8 years ago
Evo had an alternative idea; An UpgradeBee-like item that we could rez out, that would redistribute updated scripts into everyone's existing titlers. Quote from Casper Warden:
[10:09] Casper Warden: We do it in a slightly different way, server-based, but generally you'd... 1) Send a message with llRegionSay, 2) Authenticate that message in the device. The device then sets a random PIN with llSetRemoteScriptAccessPin, and transmits it back to the "bee" with llRegionSayTo. 3) The "bee" then uses llRemoteLoadScriptPin to send a "maintenance" script, which clears out all of the existing scripts in the object, and lets the "bee" know when it's done. 4) Then the "bee" sends the replacement scripts, and the pin is set back to zero which disables it.
The only way i could see that failing is if they are not actually on sim. in which case we wait or we give them an object that contains the "bee" or just flat out the new object.
Ok after a lot of debate and collaboration. the update system will be outlined as follows.
I think having an update deployment system tied to the DB would be a fast simple way to check software versions and deploy new products. Everyone in group should be on file in the accounts table. Setting up a product table for product versions wouldn't be that hard and could be easily in world driven for distributing products using an