* [EMAIL PROTECTED] (David Megginson) [2002.12.05 09:45]: > Christian Mayer writes: > > > The missing functionality is the ability to figure out if the tile has > > changed IIRC. > > > > But that'n no problem - HTTP already supports that. IIRC it send's a > > status code of 302 if the reqested data didn't change... > > Exactly -- as long as the files are available unpacked in the standard > directory structure via HTTP, everything should work just the same.
We would need to preserve the timestamp for the 302 code stuff to work. The biggest difference between rsync and HTTP is that rsync downloads diffs[1] while HTTP must download the entire file. This is a big plus for people with slow connections. I guess _my_ question in regard to rsync is how much would rsync actually help in our case. If a tile is changed -- say we fixed a runway or something -- would a diff accomplish anything since we have binary scenery files that are also gzipped? Would the rolling checksums that rsync does all end up being different, so we are always downloading the entire file anyway? If this is the case, then rsync's main advantage is worthless to us. [1] ftp://rsync.samba.org/pub/rsync/tech_report.ps -- Cameron Moore / Why are they called buildings, when they're already \ \ finished? Shouldn't they be called builts? / _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
