rmitchel@bbn.com (Rob Mitchell) (01/16/91)
SUBJ: AppleTalk ATP/NBP calls in Think C
Below are just a few questions/issues concerning Inside Macintosh
Volume 5 and Think C implementation of Preferred AppleTalk Interface
calls. Looks like there's more than meets the eye here:
[1] How do you send ATP messages in Exactly-Once (XO) or
At-Least-Once (ALO) transaction mode? In IM-V, the
Preferred AppleTalk Interface has parameter blocks for
ATP calls which are much different from the Alternate
AppleTalk Interface in IM-II.
[2] Has anyone defined the parameters the Preferred AppleTalk
Interface uses into pseudo-code or some kind of interface
spec.??? If so, we are in desperate need for it and would
greatly appreciate if you could pass it on.
[3] Do AppleTalk Parameter Blocks have to be allocated as
pointers or can you create something like:
typedef MPPPBptr *MPPHandle;
MPPHandle mppPbHndl;
OSErr theErr;
EntityName enArray [10] = { ... };
for (i=0 ; i<=NUM_NVE ; i++)
{
mppPbHndl = (MPPHandle) NewHandle (sizeof (MPPParamBlock));
(*mppPbHndl)->MPPentityPtr = (Ptr)&enArray[i];
(*mppPbHndl)->ioCompletion = NULL;
theErr = PRegisterName ((*mppPbHndl), TRUE);
DisposHandle (mppPbHndl);
}
[4] I tried the above and it doesn't seem to work. I'm not sure
if the AppleTalk Drivers (.MPP, .ATP, .XPP) actually use the
pointer passed to it or if they "alloc" there own storage.
If I use unpurgable or immovable memory, then I must keep track
of each and every protocol message requested and responded...
RIGHT???
Thanks in advance for your opinion!! If anyone has some sample code
using the Preferred AppleTalk Interface calls, I'd greatly appreciate it.
Rob Mitchell
BBN Systems & Technologies
rmitchel@vax.bbn.com
(617) 873 - 4041
These opinions are mine and mine only. They do not represent BBNs' opinions.
Rob Mitchell
BBN Systems & Technologies
rmitchel@vax.bbn.com
(617) 873 - 4041
These opinions are mine and mine only. They do not represent BBNs' opinions.