 | | Re: [MODEL] Boogie.dat
|
| (...) I think my browser (Netscape 4.x) is doing the same thing -- but not necessarily in that order -- ldraw.cgi first, then random filenames. Here's the algorithm I believe Netscape is using: - Look for an empty spot to download the file into the (...) (26 years ago, 22-Oct-98, to lugnet.cad)
| | | | | Re: [MODEL] Boogie.dat
|
| (...) <snip interesting algorithm guess> Maybe, but how would it know to choose .dat as an ending? I repeat, that is what it was doing, OR, I was hallucinating (not out of the realm of possibility). ++Lar ======== Posted via the LUGNET discussion (...) (26 years ago, 23-Oct-98, to lugnet.cad)
| | | | | Re: [MODEL] Boogie.dat
|
| (...) Because somewhere on your system there is a mapping: application/x-ldraw -> .DAT or perhaps there is a pair of mappings application/x-ldraw <-> LDLITE.EXE .DAT <-> LDLITE.EXE and the browser is treating them as transitive...? To be sure, there (...) (26 years ago, 23-Oct-98, to lugnet.cad)
| | | | | Re: [MODEL] Boogie.dat
|
| Todd Lehman writes: <SNIP> (...) It's more of an A --> B --> C where A = mime content application/x-ldraw, B = .DAT file type, C = registered application for filetype B. Also file naming definitely seems to be something that the client handles. On (...) (26 years ago, 23-Oct-98, to lugnet.cad)
| |
