Confirmed users
381
edits
| No edit summary |  (→Goals) | ||
| Line 34: | Line 34: | ||
| Taras crazy stuff: | Taras crazy stuff: | ||
| * http://zsync.moria.org.uk/ content that changes a little bit, but frequently | * http://zsync.moria.org.uk/ content that changes a little bit, but frequently | ||
| * Can also do this for web cut/n/paste. Server could insist on serving zsync summaries of common files(eg css libs, js libs like jquery) and client would do a distance search locally to see if it has anything similar and then only do range requests needed to construct the new version. | |||
| <code> | <code> | ||
| Currently we send if-modified-since: | Currently we send if-modified-since: | ||
| Line 43: | Line 45: | ||
| ** server can determine when client got nothing in cache(eg no if-modified-since), do spdy-push from a preset profile | ** server can determine when client got nothing in cache(eg no if-modified-since), do spdy-push from a preset profile | ||
| ** server could spdy-push partial files(eg only css that gets used) + zsync of rest of contents so client can request missing pieces for other pages on the website(this can hugely reduce transfer sizes)...If i remember correctly from https://bugzilla.mozilla.org/show_bug.cgi?id=834865 70%+ of css is leftover cruft...Note this might be easier to do having sites be aware of this and bundling a library that supports having css/js broken up into multiple files & supports waiting on missing pieces | ** server could spdy-push partial files(eg only css that gets used) + zsync of rest of contents so client can request missing pieces for other pages on the website(this can hugely reduce transfer sizes)...If i remember correctly from https://bugzilla.mozilla.org/show_bug.cgi?id=834865 70%+ of css is leftover cruft...Note this might be easier to do having sites be aware of this and bundling a library that supports having css/js broken up into multiple files & supports waiting on missing pieces | ||
| == Background == | == Background == | ||