Congratulation for the project, it is an amazing idea and a brilliant execution. By reading the source code i noticed that the cache uses the links in a page, thus the html those link generates, as data transmitted between peers.
While this approach is effective for blogs, news sites and in general non single app applications, in the single web app application scenario it might not be so effective since a link does not lead to new assets/html but a change of the dom by the underlying javascript execution.
Instead in this scenario seems that being able to cache the assets as images, fonts, css and js would be an effective approach.
Is there any plan or thought toward this sceanario ?
Hi,
Congratulation for the project, it is an amazing idea and a brilliant execution. By reading the source code i noticed that the cache uses the links in a page, thus the html those link generates, as data transmitted between peers.
While this approach is effective for blogs, news sites and in general non single app applications, in the single web app application scenario it might not be so effective since a link does not lead to new assets/html but a change of the dom by the underlying javascript execution.
Instead in this scenario seems that being able to cache the assets as images, fonts, css and js would be an effective approach.
Is there any plan or thought toward this sceanario ?