Re: MacBinary 4 format
Re: MacBinary 4 format
- Subject: Re: MacBinary 4 format
- From: Mike Cohen <email@hidden>
- Date: Wed, 28 Jul 2004 14:16:18 -0400
Yes, it was originally a way to transmit mac files via XMODEM protocol,
which is why everything was padded to 128-byte boundaries in the
original spec. It evolved into Binhex, which encoded everything in
ASCII. Macbinary is still sometimes used to encode files into a single
fork, but AppleSingle pretty much replaced it.
On Jul 28, 2004, at 1:56 PM, Mike Fischer wrote:
Am 27.07.2004 um 15:47 schrieb David Catmull
<email@hidden>:
On Jul 27, 2004, at 7:32 AM, Mike Fischer wrote:
Did you check out <http://www.rfc-editor.org/rfc/rfc1741.txt>?
It describes BinHex 4.0 which is probably what you are looking for.
If
not I don't know.
Thanks, but that isn't the same thing. BinHex is a text encoding like
Base64, whereas MacBinary is... binary.
Actually if you look at the RFC you will note that it is more than
just an encoding. Some meta data is also included as well as checksums
and both forks. But it is limited to the older HFS limits (name and
sizes) and contains no date/time information.
And wasn't MacBinary actually a transfer protocol? If you are using
HTTP then you wouldn't need another protocol layer on top of that.
_______________________________________________
macnetworkprog mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/macnetworkprog
Do not post admin requests to the list. They will be ignored.