Need some conceptual help for an update Server

As the title says, Im looking to write an update server for my products, so that my customers can simply get updates automatically from wherever they are instead of having to run to an update station.

now the basic mechanics are simple, they will just use a globalized mechanic that my self-written update stations use, just improved to prevent misbehaviour even under heavy load.

my main concern is the nature of SL´s UUID systems. I could never pick up the server and place it down again without breaking the entire system. since when I place it in inventory, the object still has the same UUID, however once I rez it down again, its not the same object, but a copy of it with a different UUID.
is there ANY way to circumvent this behaviour and make sure the UUID of the object I might at some point need to pick up will be the same when i place it down again?

alternatively, are there any pointers to writing a partly web-based solution where I could "register" an update server and change that registration when its UUID changed? I wouldnt need a database on the web yet, not before I took on the vendor system itself, which isnt going to happen very soon. I just want a way to reliably maintain communication with the update server even if it needs to be transported to another sim, which isnt likely, but may still occur at some point

i would let the server make a http-Request to an external php file that handles further actions if server key changed,
puts it into a text file and also gives the key to your items trying to contact your server.
=)

This idea seems a little complicated, but perhaps less complicated than going to the web.

Could you use 2 servers? One being primary, the other as a “backup”. Before transporting the primary server you indicate through existing communications that the backup server is now primary. Transport the server and set it back to primary with the new key.

Tricky, but it’s an idea.

Without storing your server's UUID offsite somewhere you will never be able to assure that your update server will work. You could have 100 "back up" servers but the product you want to update still has to have a constant means of communicating with any of them. The only way that could possibly work would be to have the main and backup servers both rezzed, send out an update on the main server with the backup server's UUID and hope that everybody happens to be online to get the update and then send yet another update after the main server is taken into inventory and rerezzed.

Hi Psistorm ,



that is not totally right If you take them into inventory you are right on next rezzing they get a new UUID, but right clicking on a rezzed object and choose "f.e. more->attach->right hand", then teleport to new location and drop the object will not change its UUID. This is a common way to transport a server from one SIM to the other.

But the main problem I see with an update server that is located only within SL and relys on the UUID - when the asset servers are acting up and you loose your server - what is not unlikely these days - then you do not have any backup!

Regards,
Shyan

I have an idea, but I haven't done it yet: use a gmail account.
With gmail you can filter messages, for example if you get a message with the subject "Update" it will be redirected to another mailbox. So that mailbox would be the server's key. If you key changes you change it in the gmail filter.

But how would your product retrieve that UUID? Sending it somewhere is one thing....being able to actually use it once it is there is another.

:Edit:
Oh wait. Sorry, I guess I read that wrong. The forward-to email address would be the update server's UUID? That would rely on external email to a prim....I have seen those emails take as long as 12 hours to be received by the prim if they are received at all.

Really? That's a turn off, lol.