Xref: utzoo comp.mail.misc:4130 comp.sys.mac.comm:1243 comp.sys.mac.system:1789
Path: utzoo!attcan!uunet!world!decwrl!shelby!msi.umn.edu!cs.umn.edu!paperboy!boombox.micro.umn.edu!mpm
From: mpm@boombox.micro.umn.edu (Mark P. McCahill)
Newsgroups: comp.mail.misc,comp.sys.mac.comm,comp.sys.mac.system
Subject: Re: Applelink to Internet gateway.... ???
Message-ID: <1990Oct13.000925.14524@paperboy.micro.umn.edu>
Date: 13 Oct 90 00:09:25 GMT
Sender: news@paperboy.micro.umn.edu (News Source)
Organization: University of Minnesota
Lines: 26
References:<34255@cup.portal.com> <45338@apple.Apple.COM> <1990Oct9.154525.6073@qualcomm.com>

In article <1990Oct9.154525.6073@qualcomm.com> jwn2@qualcomm.com (John 
Noerenberg) writes:
> On 3 Oct 90, Jim Hayes writes:
> 
>> While not implemented yet, there are plans to automatically encode
>> internet "binhex" to the AppleLink attached file format, and, well, 
>> vice versa.  I don't know when, and given Erik's constant load, 
>> probably not for a while.
> 
> Time out, Jim.  Where can I find out more about the AppleLink attached
> file format?  Y'know, there's a whole bunch of folks at MIT, UMinn, 
> Berkeley, Stanford and UofI (my apologies if I've left anyone out :-))
> working on POP-based applications for exchanging compound documents. All
> these approaches are relying on BinHex as the means of exchange (as far
> as I can tell).  Seems to me we'd all profit from knowing a bit more 
> about what you're referring to.
> 

I agree. Can you tell us anything more?


Mark McCahill

Microcomputer & Workstation Networks Center
University of Minnesota
internet: mpm@boombox.micro.umn.edu