4 ms·
The odd thing is, either in shmem/mmap, or on disk cache, is most of the fetched state. A simple "tee" of the data out of QUIC would replay the load of the disp
by ggm 6y ago
The odd thing is, either in shmem/mmap, or on disk cache, is most of the fetched state. A simple "tee" of the data out of QUIC would replay the load of the disparate mark-up elements.
It's all there. The problem is deciding how to add code to save it in a rational reloadable manner.
Compared to eg ZFS snapshot: low cost copy on write, saved state. (Admittedly of data on disk, which is the goal here, but then the browser cache is on disk)
- toomuchtodo 6y agohttps://warcreate.com/ https://warcreate.com/ https://github.com/webrecorder/replayweb.page https://github.com/webrecorder/replayweb.page
- ggm 6y agoThanks! I love proof by example.
- toomuchtodo 6y agoI hope you find it helpful!