NetNews Usenet Archive 1992 #20/NN_1992_20.iso/spool/comp/sys/mac/programm/15370

Internet Message Format | 1992-09-11 | 1.8 KB

Path: sparky!uunet!haven.umd.edu!darwin.sura.net!spool.mu.edu!umn.edu!noc.msc.net!uc.msc.edu!shamash!ethelred.svl.cdc.com!ldh
From: [e-mail] (Lawrence D. Hare)
Newsgroups: comp.sys.mac.programmer
Subject: MacBinary Public Domain Code Availability
Message-ID: <[e-mail]>
Date: 11 Sep 92 22:40:49 GMT
Sender: [e-mail]
Organization: Control Data Systems
Lines: 29
X-UserAgent: Nuntius v1.1.1d9
X-XXMessage-ID: <[e-mail]>
X-XXDate: Fri, 11 Sep 92 15:35:47 GMT

So whump - I have MacTCP TCPing and everything works only my binaries are
no more. 'course I knew this was going to happen and I have just
retrieved the specs of the MacBinary I and II standards. So - next
question:

Are there any C coded, public domain, publicly available, interface
functions that meet these specs available?

Should I go with MacBinary I or II? Guess II...

As this requires binary transfer across networks, using Unix systems as
staging posts, MacBinary is NOT a requirement - so is there any other
means of sending a file and retaining file attributes. I could create a
new resource, add in the creator and type, and then send the file. When
received I check for the resource, if not there I assume it is a text
file. If it is there I remove the resource, set the attributes and Bob's
yer Uncle! 'corse, this might be a problem for files with no resource
fork, like spreadsheets. I could add one, then add my resource. When I
retrieve the file I remove the resource fork, or have the fact that there
is no resource fork as an attribute in my new resource, so when I
retrieve the file I just create the data portion. And so on...

Any ideas?

Thanks...
--
Lawrence D. Hare       Control Data - Silicon Valley Operations
Consultant             Voice: [phone] - C/N [234] 4339
[e-mail]        Mail: SVLa60  FAX: [phone]