
www.Usenet.com
| <-- __Chronological__ --> | <-- __Thread__ --> |
On Mon, 01 Dec 2003 17:09:36 -0500, Robert L. Bass wrote: > I sometimes use self-extracting executables to deliver large groups of > related files (PDF, HTML, DOCs, images, etc.). It makes it easier to > maintain links if the component parts are unzipped into the specific > directories I designed them for. A ZIP file can do that too. I hesitate to download an .exe even if it is just an executable self expanding .zip... > What if the eBook includes integrated flash HTML can handle this... > or other apps? What sort of app are you talking about? If it's an app it's not content... > Most of the tim I do. But there are things I'd like to include in a > future release that *may* (I'm not sure yet) be better served via an > exe. There's no content that is better delivered as an executable. There's no reason to do it. > If you scan it and it's got some nasties inside, sure. I don't trust a scanner to tell me if an executable is safe. An executable, by it's nature, can do just about anything, and my scanner may not be able to tell me about it. > If it's stated on the page that "this is an executable" then the vendor > may indeed be reputable (or not). If I trusted the vendor it wouldn't be an issue. I don't trust most vendors. Bottom line: I would never download an executable that was supposed to contain content (a book, a picture, etc.). I would recommend to anyone else out there to follow the same guideline ;) -- Lenroc
| <-- __Chronological__ --> | <-- __Thread__ --> |