External asset support over HTTP.

I don't know if I posted this here yet, but...
llSetTexture("http://www.myserv.net/eggy.jp2";
llTriggerSound("http://www.myserv.net/eggy.ogg";
llRezObject("http://www.myserv.net/eggy.slc";

Give the old asset server some rest!

Good idea, but perhaps it needs higher level of redirection. Your method works great in scripts, but everything else (building and preview dialogs, unscripted objects) couldn't take advantage of this remote object method.

Although it still uses the asset server, something way more flexible and fun would be to leave those calls as-is and instead, all object types could be assigned a URL as a property, with the "real" object acting as a proxy if the URL doesn't respond within a certain time period. This way, if the remote server is pooched or no longer online as months pass, things you buy that use these remote-referenced objects don't totally break. It would be nice to add an auto-refresh rate to those URLs as well...

Your llRezObject("http://www.myserv.net/eggy.slc"; is the most interesting because it implies being able to save objects remotely or have a server generate them on the fly.

Drool... also you can just change "eggy.jpg" on the server and have it reflect on all objects using it in world. Think web based configuration for vendors/picture frames/ao's/etc...