09-18-2020, 01:27 AM
Quote:But he's already done this for the launcher and client files - so it's just a case of modifying the existing code for blueprints.
Do you know the how the game is programmed so that you can make claims about the reusability of the current code, and how long it would take to adapt it? The launcher could just be getting some set of files configured statically on the server, which is a little bit different from arbitrary new files being added by players during gameplay (assuming they are stored on the server as separate files).
Quote:Anything is more efficient than that by comparison
I think this is true as long as "anything" excludes using the mechanism for partial updates for downloading the entire library. If there are several new designs, you have a good download speed, and you have a high latency to the server, though, it's possible an individual update might take longer than downloading the full update currently does, because the overhead of making all the requests might be larger than the download time saved. For example, a european with 100Mb/s download speed and 200ms ping would download the entire library in less than two seconds, but just the overhead from making requests to download 10 new ship designs would take up two seconds. In the common case this won't happen, and this cost gets spread out anyway so that the total amount of time spent downloading across all design listing updates will almost definitely be smaller. I'm not saying that he needs to implement batch requests to make caching designs an improvement, but it's needed to guarantee that it's a straight improvement always with no tradeoffs. And anyway the code changes required may not be trivial even without this feature.