2

Only download changes to client after the experience is once downlaoded complete.

Richardus Raymaker

December 25, 2017 07:26

None

Follow

I have the idea, not sure how easy it is to implement.

If a user have downloaded th whole experience one.
And then the experience get a few small changes.
It would be interesting and good to only send the changes to the user.
It makes it faster to download a updated experience. It saves bandwidth,
2 things users really like to see.

Except i think currently the whole experience is one big file that get send to the user. That makes the download faster then lot's of small files.

Request: Only send updated content to user  if the whole experience is already in the cache.

See alos: https://help.sansar.com/hc/en-us/community/posts/115020416523-Offline-experience-cache-pushing?page=1#community_comment_115005480863

1 comment

• 0
  
  Galen December 25, 2017 18:43

  This is feasible, actually. When publishing, it would be possible to take the manifest, a list of asset IDs used in a scene, and compare it to the previously published manifest. Any new assets added or changed would be collected into a "delta" manifest, a list of only those changes. And a compressed package would be created with only those changed assets. A second package would be created with the entire scene packed into it.

  When your client wants to visit a scene, it would request the scene and indicate which version of the scene you currently have cached. If you visited three versions ago, the server would feed you the last two update packages, containing only things changed during those updates. The total should be smaller than downloading the entire scene. If the person had never visited before, they get the full package.

  The server would not need to keep all past update packages for this to work. One option would be to only keep updates from the past N days. Or even to add up the sizes of all update packages going backward. At the point where the sum of sizes of updates is greater than the size of a full download, you cut off any updates prior to that. When a client declares it has version N cached and the earliest update package is N+2 (or higher), there is no update to bridge the gap, so the client downloads the full package.

  There are various ways to tweak this to balance everything here, but the bottom line is that the file storage on the server should never need to be more than double what it is in today's sceme in order to store both a full download and the incremental updates that would speed up getting you into the scene.

  Another approach might be to segregate large assets like long audio files from the download packages and download those assets separately. Those will only infrequently change, so they can be downloaded once and not need to be re-downloaded just because a small thing in a scene changed. And if those assets get used in multiple scenes, all the better. This is a hybrid between SL's every-asset-downloaded-separately strategy and Sansar's all-assets-in-one-package strategy.

  Edited by Galen December 25, 2017 18:48