Welcome to the Second Life Forums Archive

These forums are CLOSED. Please visit the new forums HERE

Updating products?

Kitten Lulu
Registered User
Join date: 8 Jul 2005
Posts: 114
03-02-2006 15:19
How do you handle product updates?

I have two products, one is no-copy, the other is no-transfer. Both were broken by the last SL update. I am going to have to handle out the fix manually to all my customers.

I don't want to do it ever again. Any idea about how to handle it automatically?

I can build an external server, if I need a database. I am just not sure how to handle the update of the no-copy product.
_____________________
I've got a blog!

My products are available on SLExchange or in-world in my shops: Kitten Lulu's Emporium and Kitten&Co.
Till Stirling
Crazy Inventor
Join date: 31 Jul 2004
Posts: 124
03-03-2006 00:06
I have created a voucher system for that and am going to add that to those products, that are no-transfer. A user can then easily request a a replacement/update by using the voucher. The item is delivered by an inworld server. The system is also available for sale.

Till Stirling
_____________________
Osgeld Barmy
Registered User
Join date: 22 Mar 2005
Posts: 3,336
03-03-2006 10:49
a quickie way is to have the object check its owner on rez, i usually save their key in a child prims discription feild, and email it off to me, if the owner changes send both keys to email and record the new key in the discription feild.
Keknehv Psaltery
Hacker
Join date: 11 Apr 2005
Posts: 1,185
03-03-2006 15:12
It seems as if the question wasn't really answered.

For transfer, no-copy objects, I would recommend having the object do the normal update procedures, and when it detects that an update is available, it directs you to your store. Then, you drop the object into a prim, which will give you the updated version.

For no copy, no transfer... Perhaps rez it near the update prim, and have it able to receive a command "update", which will set up a listen and llSay something on a channel that the updater is listening on. When the updater hears this, it sends a command to the other object to die, and sends the owner the updated version.

There are few minor additions to these schemes needed to prevent spoofing, but they should work.