Difference between revisions of "Scripted Object Return"
Gigs Taggart (talk | contribs) (llReturnObject) |
Pagan Bishop (talk | contribs) |
||
| Line 7: | Line 7: | ||
</pre> | </pre> | ||
A general solution might be to have an asset manager prioritize requests and just drop scripted requests if the load on the asset server is in the danger zone. | |||
Some asset server request prioritization would probably open up potential for other very useful things like automatically setting permissions on objects, etc. | |||
Another useful call to go with this might be a call to get the load on the asset server so scripts can delay their work until things are better. | |||
-Pagan Bishop | |||
[[Category:Feature Requests]] | [[Category:Feature Requests]] | ||
Revision as of 16:57, 30 January 2007
Pretty straightforward, the main question here is how to implement it without putting undue strain on the servers.
Kelly has said that they don't want to do this because of load on the servers. Surely some kind of throttling could be accomplished to make this very useful function a reality.
llReturnObject(key object)
A general solution might be to have an asset manager prioritize requests and just drop scripted requests if the load on the asset server is in the danger zone.
Some asset server request prioritization would probably open up potential for other very useful things like automatically setting permissions on objects, etc.
Another useful call to go with this might be a call to get the load on the asset server so scripts can delay their work until things are better. -Pagan Bishop