Looks nice. Taking a quick look at rsync-over-http makes me think this will work just fine over SPDY, and SPDY aims to not change the semantics of HTTP; so the content-encoding and transfer encoding should still work.
Mike On Nov 12, 3:37 pm, originalmiu <[email protected]> wrote: > Hope I found the right discussion for people who develop SPDY (http:// > sites.google.com/a/chromium.org/dev/spdy/spdy-whitepaper). > > Have the SPDY designers thought about how to efficiently handle > "frequent transmission of similar dynamic content?" In particular, > one approach is for the server to assume the client has an older > version of the content of some resource, and just send some binary > signatures which would allow the client to calculate the "diff" in the > content. The client then only needs to request the blocks of data > which have changed. > > More-complete details (as this idea is not my > own):http://rproxy.samba.org/doc/protocol/protocol.html > > I was looking at the SPDY whitepaper. Something like this could be > integrated with the "server hint" feature (see Advanced Features > section in whitepaper). > > So, what do you think? -- Chromium Discussion mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-discuss
