Adopt MacBinary II Mac File Encoding for FTP Transfers
draft-mityok-macbin1-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Tim Mityok | ||
| Last updated | 1996-07-30 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This draft is a targeted at the Macintosh Internet users to adopt the MacBinary II form of Macintosh file encoding for use on FTP sites as an alternative to BinHexing Macintosh files. The current standard file encoding method for Macintosh files placed on Internet FTP sites is BinHexing. The process converts binary data into a coded-text based format. While very popular and widely used this process increases the files size dramatically. For example a self-extracting archive that is 389,089 byte in size will swell to 535,944 bytes after being BinHexed. The resulting file is nearly 30% larger than its original version. This process is completely wasteful and totally unnecessary for FTP transfers.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)