[sldev] How Asset server handles saving of scripts

Robin Cornelius robin.cornelius at gmail.com
Wed Dec 19 13:49:04 PST 2007


Gordon Wendt wrote:
> Hi, I'm sure it's documented somewhere but for the life of me I can't
> find it but with the current asset issue that's going on I was thinking
> of how script saving is handled by the asset server, specifically since
> apparently it attempts to save each time you hit save but while it's in
> the process of saving you can make a small change (even if you change it
> back before hitting save again) then hit save which sends a second
> request and how the asset server handles that.  Obviously it has to deal
> with the second request since that's the most recent change however what
> happens to the first save attempt? and is there a way to streamline the
> way it deals with such requests since as far as I can tell that seems to
> be a fairly intensive operation especially if someone were to do so
> repeatedly (can't figure why someone would but people do strange
> things).  Just a thought.

Don't forget that you do a client side compile before the asset is
uploaded so that takes a while. And yes *every* time you press save
thats a new asset same as with notecard. But good point about making
minor changes, its a shame the asset just can't be updated but i assume
thats a whole world of additional complications?

Robin



-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 252 bytes
Desc: OpenPGP digital signature
Url : http://lists.secondlife.com/pipermail/sldev/attachments/20071219/87849af0/signature.pgp


More information about the SLDev mailing list