[sldev] How Asset server handles saving of scripts

[Hamncheese]

No I'm not sure about anything I said and I wasn't when I said it. Based on 
Kelly's description, I went back and did a packet sniff on a script save 
that is in object inventory and a script save that is in regular inventory. 
I'm going to have to dig into my CAPS vs legacy assumptions. It is clearly 
pushing the script in clear text through UDP to 63.210.157.63:13006 in both 
cases but I'm not sure if that is the whole story.

----- Original Message ----- 
From: Erik Anderson
To: Hamncheese
Cc: sldev at lists.secondlife.com
Sent: Wednesday, December 19, 2007 7:46 PM
Subject: Re: [sldev] How Asset server handles saving of scripts


You sure about this?  I always thought this was a caching issue, so a sim 
can say "the UUID is one that I already have, and assets cannot be modified, 
so no reason to ask for fresh content from the asset server".  The thing is, 
prims aren't affected by this "dirty write" system, why just notecards and 
scripts?


On Dec 19, 2007 3:26 PM, Hamncheese <me at hamncheeseomlet.com> wrote:

This is done probably for performance reasons. It is more performant to
insert a new row in a table than to locate, lock, and then update, release
lock.