* [EMAIL PROTECTED] (Andy Ross) [2002.12.04 13:21]: > I just tried this last night. Curt, this rocks.
I haven't tried it, but I can't wait to do so. > I think you have to give serious thought to enabling this by default, > either by adding it to the fgfs binary or by having fgfs spawn it as a > child. It turns the job of downloading, installing and updating > scenery from an annoying sysadmin chore into a trivial noop that your > proverbial grandmother could use. This is a huge, huge win. Hiding > it inside a separate executable and requiring special command line > arguments is doing casual users a major disservice -- they *want* this > feature. (Sure, some will want the ability to disable it. But the > majority of users will see a lot of benefit from having it on by > default.) http://librsync.samba.org/ It's LGPL'd and pre-1.0. Here's their current TODO list from CVS: http://cvs.samba.org/cgi-bin/cvsweb/librsync/TODO?rev=1.31&content-type=text/x-cvsweb-markup > Related to the above, you'll probably want to segregate a "release" > scenery directory from the "development" scenery to prevent > incompatible changes from being pushed to users without current code. I agree. > It occurs to me that if fgfs tries to load a scenery tile while rsync > is still pulling, you will get corrupt tile and (worst case) crash the > tile parser. Is there a need for locking or protection against this > sort of thing? Just a mail-spool-style "dot lock" should be > sufficient -- if FlightGear sees a ".terrasync-in-progress" file, it > can refuse to load the directory. [This is the cue for someone to > jump in with a discussion about all the dangers and pitfalls of > different locking mechanisms on different filesystems.] Apologies if > a feature like this is already in there, I haven't read the code. Locking an entire directory would be bad thing. We would want to do per-file locks. The simplest cross-platform solution is a .lock file for a given file. Using flock or equivalent would be a bit more complicated, but I'm not familiar with anything other than Linux. Couldn't we have a simple filelock function in SG with a bunch of #ifdef's each platform's implementation? I assume most OSes have the same abilities -- exclusive write, read, or both. > Again, magnificent feature. I love it. Yes, I can't wait to play with it. -- Cameron Moore __END__ _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
