(I apologize if I tagged too many or too little components) (edit:also I'm unsure if this should be VWR or actually SVC, I would have set it to both is possible I guess) the idea is to have the option of having things like images, prims/objects, scripts etc stored on the client machine, avaiable only when the client is connected there would be the need for additional permissions, like "can be saved offline" and "can be uploaded to agrid other than the one it was created" (the actual names don't really matter), but this would probably make it much easier for people to stay with their avatars when moving to a different grid this would also allow people to have stuff easily back-uped (if the permissions allow) as well as make the load on LL's asset servers slightly smaller ideally objects would be allowed to be rezzed "on the ground", and be temporarily used on the sim (somthing like a upload that only lasts while the person is connected to that sim) items saved offline would be allowed to be uploaded to the grid (depending on permissions and rules of the grid etc) also, somthing that isn't essential to the main idea, scripts perhaps could also be run by the client, simply communicating with the server the stuff that isn't internal to the script, this would allow people to, for example, use their hardware resources to run the scripts on their avatar as well as on their "disposable upload" objects saving plenty of resources on the server (please let me know if I should separate this part from the rest of the proposal) people would be able to use as many client-hosted images as their machine and connection can handle, sending the data directly to other clients (or perhaps optionaly using the grid as proxy) without being charged upload fees, same things for other inventory items, but things like rezzed objects, that the sim needs to know about would need to be uploaded (but as described above it would be a disposable upload). In all cases the sim doesn't need access to the exact data of the item, at most it would get it's UUID I guess there probably should be one of those warning windows you can mark "do not show this again" for the permissions to save offline and upload to a different grid letting people know that there isn't guarantee the format will not be cracked and the contents potentially replicated free of any permissions (and also perhaps mentioning that other grids might not follow the same rules about IP right etc as the current one does and things like that) the stuff would be stored as individual files, so people could save separated things to removable media etc I think probably people wouldn't be allowed to save no-copy stuff offline, since that would allow it to be copied easily perhaps the UUID for client-hosted content would be a new format, perhaps somthing like the user UUID followed by the item UUID to avoid potential conflicts and I guess it would also make it easier for the system to find where the resource is stored