Confirmed users
414
edits
Mobile/Janus: Difference between revisions
→Goals
(→Goals) |
(→Goals) |
||
| Line 45: | 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 | ||
== Implementation == | |||
We've started out implementing the proxy server using Node. It has an existing SPDY and HTTP2 libraries, and is relatively good at dealing with streamed data. Development occurs in GitHub here: https://github.com/mozilla/node-janus | |||
We also have a mailing list where folks can talk about all things related to the project: https://mail.mozilla.org/listinfo/janus-dev | |||
== Background == | == Background == | ||