Distributing a system to others - approaches???

Hi,

Just wondering how scripters cater for giving/selling a system to others, so that someone else then will host (rez) and manage (perform admin, necessary script restarts) the system? Are there any general guidelines/approaches/good ideas people have on this?

Aspects I had in mind included:

1. administrator approach - how to identify an administrator in the system? e.g. use object owner, hard code admin uuids, include a addAdministrator() function so that the owner can manually add another administrator to the system themselves, other approaches?
   
2. system state on sale/give - i.e. would the system normally be run up and initialised, then stored by builder so the system is ready to go, and then passed on. Or I guess in some cases when system objects rez only then can their true UUID be discovered so pre-initialisation is hence not possible.
   
3. use of on_rez() and state_entry() and how they would be used (depends on which admin approach is used no doubt)
   

Tks in advance

bump (would still be quite interested in what people are doing here)

I think there are a wide range of options...

Getting the owner at rez or intialisation and then allowing the owner to do stuff is one option - including adding names of avatars who can 'administer' the system. or use a notecard of the names.

If reacting to voice commands, for security you might need to make sure the command is coming from an *avatar* with the given name.
Of course, if you already have the key of the avatar, you can just check that instead.

Having one object rez another can be a useful wayof initialising data. Ive used that myself so that the original owner can rez something that can be given away, but which remembers who 'rezzed' the copy.

But Im no expert on this... Ive only just begun playing around.