Re: MacBinary 4 format
Re: MacBinary 4 format
- Subject: Re: MacBinary 4 format
- From: Mike Fischer <email@hidden>
- Date: Wed, 28 Jul 2004 19:56:01 +0200
[Second try. I used the wrong mail account initially.]
Hi David,
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.
I've found definitions for
MacBinary 3, but I see lots of references to MacBinary 4. I don't know
what the difference might be (maybe long file names?).
I see, but I never heard of it and as others have responded it doesn't
seem to exist.
BTW: Where is the connection to the MacNetworkProg mailing list?
Sounds a bit OT to me (though the volume here is so low that it
doesn't matter much.)
I figured it was appropriate since networking apps are practically the
only place MacBinary is used; I'd welcome any suggestions for other
places to ask. I'm looking for a good standard way of transmitting both
forks of a Mac OS file via HTTP.
I didn't mean any offense. When I saw your message I just thought that
a question about file formats seemed somewhat inappropriate. But I do
see the connection now.
As to the Question... no idea. Stuffit sitx comes to mind but that
proprietary I guess. There is also AppleSingle and AppleDouble which
are documented and somewhat standard. Not sure if these formats handle
long Unicode names though. The Panther Finder zip archive format could
also be considered standard, depending on your needs.
The word standard seems to imply that something at the receiving end
will know the format. Is that something under your control? If so it
might be easier to define your own format. It's not too hard to do.
Mike
--
Mike Fischer Softwareentwicklung, EDV-Beratung
Schulung, Vertrieb
Web: <
http://homepage.mac.com/mike_fischer/index.html>
Note: I read this list in digest mode!
Send me a private copy for faster responses.
_______________________________________________
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.