Thread Previous • Date Previous • Date Next • Thread Next |
On 2017-02-17 09:30 AM, Wayne Stambaugh wrote:
On 2/16/2017 6:19 PM, Oliver Walters wrote:iii) Excessive bandwidth - Each time a .pretty lib is loaded, it downloads a zip of the entire library? If we were making use of git functionality it would be simple to just update the library (and store a local cache) and thus only download the diff rather than re-download the entire thing.Once again, a git plugin solves this problem nicely.
Bandwidth can be saved by saving .pretty libs on the local hard drive instead of temporarily caching them. It also means ones that have been previously requested will be available even when the computer has no net access.
When someone needs a .pretty lib you check if it is already on the local drive. If not, download it and save to the local drive. If the library is already on the local drive check the time and date of the remote copy. If the remote version is newer than the local copy download library and save it to the local HD.
That's the simple way to reduce bandwidth requirements. The "download" portion of the process could involve using source code control to update the local copy instead of downloading the entire library.
-- Cheers! Kevin. http://www.ve3syb.ca/ |"Nerds make the shiny things that distract Owner of Elecraft K2 #2172 | the mouth-breathers, and that's why we're | powerful!" #include <disclaimer/favourite> | --Chris Hardwick
Thread Previous • Date Previous • Date Next • Thread Next |