[sldev] How Asset server handles saving of scripts

[Gordon Wendt]

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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.secondlife.com/pipermail/sldev/attachments/20071219/f385428d/attachment.htm