Xref: utzoo talk.bizarre:41739 comp.society.futures:1464
Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!usc!sdsu!ucsd!helios.ee.lbl.gov!pasteur!ucbvax!bloom-beacon!eru!luth!sunic!draken!ianf
From: ianf@nada.kth.se (Ian Feldman)
Newsgroups: talk.bizarre,comp.society.futures
Subject: Telepathic data transmission protocol
Summary: Project status report
Keywords: where is it now that I need it?
Message-ID: <2545@draken.nada.kth.se>
Date: 15 Dec 89 11:13:29 GMT
Reply-To: ianf@nada.kth.se (Ian Feldman)
Followup-To: talk.bizarre
Organization: Royal Institute Of Technology, Stockholm, Sweden
Lines: 27


In a private and quite probably definitely non-redistributable message
to the undersigned, <xy@z.domain> (Name Witheld To Protect The Innocent)
writes re: the state of the telepax transmission protocol project:

>      Well you see, brilliant breakthrough though it was, it really
> didn't help US a lot; we're in R&D you see - and marketing use it to
> communicate specifications to us (and still continue to do so).  The
> trouble is that it isn't immediately error-checked - and indeed the
> receiver doesn't even get a conclusive carrier-detect.  Thus, a typical
> transaction log goes something like this........ 
> 
> % pathnet software-group
> Connected to software-group
> Thinking......
> software-group> "I think what marketing probably want is xyz"
> software-group> Implementing xyz. Will take 3 months.
> software-group> send xyz to marketing
> marketing> packet error!. did not request xyz! retry!


  Well, clearly one can see there's them brains at work here... watch
  this space for forthcoming progress reports from the field.


--Ian Feldman /  ianf@nada.kth.se  ||  uunet!nada.kth.se!ianf
             / "Bytes, bytes, bytes, bytes..." Shakespeare recompiled