Tony Peden wrote: > > On Wed, 2002-12-04 at 12:47, Christian Mayer wrote: > > Cameron Moore wrote: > > > > > > * [EMAIL PROTECTED] (Christian Mayer) [2002.12.04 14:05]: > > > > Norman Vine wrote: > > > > > > > > > > Andy Ross writes: > > > > > >> > > > > > > I think you have to give serious thought to enabling this by default, > > > > > > > > > > Great idea, got a URL for a native WIN32 version of rsync ?? > > > > > > > > IMHO we should switch to HTTP. > > > > > > > > This avoids firewall problems and clients are also easy to get. > > > > > > Are you playing with FG at work? :-) > > > > No. And chances are my firewall at home does work... But I don't know > > how the firewall at my univeristy is configured (and I'm allowed to use > > FGFS there...) > > > > Anyway, I can understand anybody who denies as much as possible in the > > firewall config (doesn't matter if it's at work or at home). And opening > > a port just for FGFS for a protocoll that can be replaced with a > > protocol that passes through most firewalls flawlessly doesn't seem like > > good practice. > > > > Oh, and changing to HTTP would allow proxies to cache the scenery... > > Except, as Curt has already pointed out, rsync is more than just a > file transfer protocol ... its functionality would need to be duplicated > in FG/SG/plib before http could be used.
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... CU, Christian -- The idea is to die young as late as possible. -- Ashley Montague _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
