Austin Middleton
Austin Middleton
The method should close the store and delete the underlying database
In previous discussions we have concluded that a simpler public interface would be beneficial and include the following methods: * constructor * update * fetch * getFile The remaining public...
Snapshots should automatically be cleanup when they are stale or the cleanup functionality should be exposed in the api.
When an update is found a new snapshot is created, the snapshot is downloaded from scratch despite the high likely that older snapshots already contain some of the needed data....
The landing page should be served over planktos if the browser supports it. Also a live demo section should be added that informs the viewer that the page was downloaded...
When update() is called, it makes 4 http requests which makes calling update() frequently infeasible. The files requested everytime update() is called: * `planktos/root.torrent` * `planktos/manifest.json` * `planktos/install.js` * `planktos/planktos.min.js`...
The current way the downloader is injected into web pages leaves a lot to be desired. This issue is more of a tracking issue than one that provides a solution....