[sldev] How Asset server handles saving of scripts

[Gordon Wendt]

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