I strongly agree with the general direction of adding some 'harmless' binary
header. And, while we're talking about it, why not adding the 'expected file
size' in it?! This way the image could check immediately if something's
obviously broken.

  Andreas
--
+===== Andreas Raab ========= (andreasr at wdi.disney.com) ==+
| Walt Disney Imagineering        Phone: +1 818 544 5016  I
I Glendale, CA                    Fax:   +1 818 544 4544  I
+======< http://isgwww.cs.uni-magdeburg.de/~raab >========+


> ----------
> From: 	Dan Ingalls
> Reply To: 	squeak at cs.uiuc.edu
> Sent: 	Tuesday, May 11, 1999 2:53 PM
> To: 	squeak at cs.uiuc.edu
> Cc: 	recipient list not shown
> Subject: 	Re: Linefeeds in Squeak source code
> 
> Folks -
> 
> I just thought of another possibility.
> 
> Does anyone know whether there are guidelines for deciding that a file is
> "text"?  For all I know, if the first 100 characters (ie the version
> banner) contained a couple of weird character codes, it would suffice to
> discourage all the standard network programs from messing with it.
> 
> 	- Dan
> 
>