David Luff wrote:
David Luff writes:
Is it likely to work over a 56K modem?
Well, it mostly worked. After starting in an area with no scenery, it took
a couple of minutes waiting before the appropriate airport came down, and
FlightGear could be restarted properly. Flying the C172, terrasync mostly
kept up, but in both my tests (one in the bay area, one in the relatively
sparser UK) managed to miss one tile. I may be mistaken, but it appears to
download a whole 1x1 degree area at once in alphabetical order, and there
were times when nothing was coming down,
I had a very similar experience. I think the pauses were because the
rsync server was busy; one or two local rsync processes were always
active, but often seemed to be waiting for data. The local TerraSync
would create another immediately when I killed them. I then switched
airports, but it did not cancel the current rsync processes so nothing
was fetched for the new location until all the outstanding fetches
completed (or, in fact, were killed by me).
so I think that if the order of
the tile download within a 1x1 chunk was optimised to get the closest
first,
That would be more difficult. In the normal (intended) scenario, when
you have already got the current degree chunk, it doesn't matter much in
what order it fetches the insides of the chunk ahead, so Curt just asks
rsync to get the whole directory. Cancelling outstanding rsync
processes would also be considerably more difficult (to do portably).
and if downloading was continued almost continuously based on
position and heading, then I'm quite sure it could be made to keep up no
problem.
I think that is what it is trying to do already.
Very impressive stuff anyway.
Absolutely.
- Julian
_______________________________________________
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
