Xref: utzoo comp.sys.mac.programmer:21029 comp.lang.c:35538
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!usc!apple!claris!outpost.UUCP!peirce
From: peirce@outpost.UUCP (Michael Peirce)
Newsgroups: comp.sys.mac.programmer,comp.lang.c
Subject: Re: AppleTalk / C Programming Problem
Message-ID: <0B010004.supkkq@outpost.UUCP>
Date: 26 Jan 91 23:47:30 GMT
Reply-To: peirce@outpost.UUCP
Organization: Peirce Software
Lines: 25
X-Mailer: uAccess - Mac Release: 1.0.3


In article <1991Jan26.151519.1@telematik.informatik.uni-karlsruhe.de>, schaefer@telematik.informatik.uni-karlsruhe.de writes:
> 
> If you look at "Inside Macintosh Vol II" Page 283 you come to know
> that the destination-socket must not be in the same node as the source-
> socket. 

Not necessarily true.

There is a call called SetSelfSend that allows AppleTalk to work intranode
in addition to the normal internode.

Many programs and inits turn this on (Public Folder for example turns
on self send).  There's even an init that someone wrote that does
nothing els, but turn self send on.

It's very helpful when debugging network code without having to transfer
the programs around.  (You do have to make sure you are doing things
asynchronously though, or it hangs).

-- michael


--  Michael Peirce         --   outpost!peirce@claris.com
--  Peirce Software        --   Suite 301, 719 Hibiscus Place
--  Macintosh Programming  --   San Jose, California 95117
--           & Consulting  --   (408) 244-6554, AppleLink: PEIRCE