[sldev] How Asset server handles saving of scripts
Hamncheese
me at hamncheeseomlet.com
Wed Dec 19 15:26:00 PST 2007
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.
Also, I'm pretty sure that script uploads go through CAPS today. The client
side compile, then upload model (see LLPreviewLSL::uploadAssetLegacy) is
being ditched in favor of upload file over HTTPClient::Post (see
LLPreviewLSL::uploadAssetViaCaps).
Part of the disconnect of the missing asset problem is that when LL
personnel (QA, etc) run SL they go through legacy instead of CAPS (from what
I can tell). What I think the developer forgot in the CAPS model is that
HTTP is not guaranteed delivery (upstream or downstream).
I think to get a definitive answer, you need to talk to someone at LL,
because all this is largely guess work on my part.
----- Original Message -----
From: Harleen Gretzky
To: Gordon Wendt ; sldev at lists.secondlife.com
Sent: Wednesday, December 19, 2007 5:46 PM
Subject: Re: [sldev] How Asset server handles saving of scripts
Nothing is overwritten, each save is a new asset with a new UUID.
----- Original Message -----
From: Gordon Wendt
To: sldev at lists.secondlife.com
Sent: Wednesday, December 19, 2007 4:58 PM
Subject: Re: [sldev] How Asset server handles saving of scripts
It would be nice if the client sent a drop request before the new save went
in that way any pending requests server side were removed before the new one
came in, that would save load I think since instead of having to deal with
one request that would be immediately overwritten once the second one went
through it could deal with the first one and if s second one came through
immediately drop the first to work on the next one in the queue which is
possibly the second request. We're probably not talking a huge difference
here but with heavy asset loads every little bit counts especially when each
one is compounded by script saves constantly across the grid.
On Dec 19, 2007 4:49 PM, Robin Cornelius <robin.cornelius at gmail.com> wrote:
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
_______________________________________________
Click here to unsubscribe or manage your list subscription:
/index.html
_______________________________________________
Click here to unsubscribe or manage your list subscription:
/index.html
More information about the SLDev
mailing list