home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.mail.mime
- Path: sparky!uunet!haven.umd.edu!darwin.sura.net!ra!atkinson
- From: atkinson@itd.nrl.navy.mil (Randall Atkinson)
- Subject: Re: Using MIME without extra mail headers
- Message-ID: <C0LnHt.C9J@ra.nrl.navy.mil>
- Sender: usenet@ra.nrl.navy.mil
- Organization: Naval Research Laboratory, DC
- References: <1993Jan8.211048.21332@infodev.cam.ac.uk> <C0LA9I.9AB@ra.nrl.navy.mil> <1993Jan9.143137.29608@infodev.cam.ac.uk>
- Distribution: na,uk
- Date: Sat, 9 Jan 1993 18:32:16 GMT
- Lines: 27
-
-
- In article <C0LA9I.9AB@ra.nrl.navy.mil> atkinson@itd.nrl.navy.mil (Randall Atkinson) writes:
- >MIME works fine as is with gopher. I can't imagine a reason why it
- >wouldn't work fine with ftp as well. There is serious discussion of
- >adding MIME to USENET news as a new enhanced article format.
-
- In article <1993Jan9.143137.29608@infodev.cam.ac.uk> ag129@cus.cam.ac.uk (Alasdair Grant) writes:
-
- % Forgive me for being stupid, but MIME states that certain
- % information necessary for unpicking the text should be carried in
- % message headers by the use of new header fields. FTP does not have a
- % concept of message (or file) headers. If it does "work" with FTP
- % (e.g. to allow the correct transmission of mixed text/binary files
- % between systems with different character codes, which is one
- % application I have in mind) it does so by some method not described in
- % RFC 1341.
-
- Ah, I didn't follow your ftp thinking fully. ftp indeed cares not
- about anything internal to the file it is moving and it should never
- ever look inside a file. Normally one can safely move mixed content
- files via "binary" mode ftp transfer. I would not consider it
- desirable to have an ftp that looked inside the bits it was moving
- around (personal opinion).
-
- Ran
- atkinson@itd.nrl.navy.mil
-
-