[comp.protocols.appletalk] ATPL is really atpl

aw0g#atalk.errors@ANDREW.CMU.EDU (03/15/88)

It is lower case 'atpl', and I spent a long time debugging till
I discovered what Paul Menon just said.
...
Apple recommends (and I heartily agree) that anyone using ATP go the
extra step and not use the 'glue' routines provided by 'atpl'.  Instead
use the PB - style calls.
...
Cheers, Pete Gaston

rcopm@koel.rmit.oz (Paul Menon) (03/17/88)

in article <2837643@um.cc.umich.edu>, aw0g#atalk.errors@ANDREW.CMU.EDU says:
> 
> It is lower case 'atpl', and I spent a long time debugging till
> I discovered what Paul Menon just said.
	Ooops, darn caps lock KEY, THERE IT GOES AGAIN!! (sorry).
> ...
> Apple recommends (and I heartily agree) that anyone using ATP go the
> extra step and not use the 'glue' routines provided by 'atpl'.  Instead
> use the PB - style calls.
	Agreed, but then why has Apple described these high level routines?
Paul.

han@Apple.COM (Byron Han, fire fighter) (03/20/88)

the old style interfaces are described for historical reasons and for
backwards compatibility.

the new style interfaces involve a tad more work by the programmer but
are preferred.  they are not that much harder to learn.  then again,
I learned the low level stuff first before learning the higher Pascal
interfaces.

I guess part of the reason that the low level interfaces are recommended
are that if there are bugs in the glue that implement the higher level
Pascal interface, you would have to recompile your application (or at least
change your atpl resource).  by using the low level stuff, you are
only relying on the apple drivers.

Hope this explains some things.
-- 
------------------------ Byron Han,  Communications Tool ----------------------
     Apple Computer, Inc.  20525 Mariani Ave, MS 27Y  Cupertino, CA 95014
 ATTnet:408-973-6450    applelink:HAN1    domain:han@apple.COM     MacNET:HAN
GENIE:BYRONHAN   COMPUSERVE:72167,1664   UUCP:{sun,voder,nsc,decwrl}!apple!han

aw0g+@ANDREW.CMU.EDU (Aaron Wohl) (03/21/88)

The atpl glue involves doing memory manger calls for each packet sent/recieved,
this tends to be slow.  Also the atpl glue is designed to send events after
each async call compleats.  The event manager isn't fast enough to really do
this well.  When a program gets a network event there is no way for it to
handle network events from desk accessories (or other switcher/multifinder
partitions).

I was confused by the atpl glue for a while.  I just assumed the assembly
language calls defined in Inside mac V2 where logicaly the same as the pascal
calls.  They are compleatly different and don't have the problems mentioned
above.  The new prefered calls bring out the assembly language interface so
that it is more usable from pascal.
Aaron Wohl