Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cwjcc!tut.cis.ohio-state.edu!att!cbnewsk!ech
From: ech@cbnewsk.ATT.COM (ned.horvath)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Notification Manager question
Message-ID: <879@cbnewsk.ATT.COM>
Date: 21 Aug 89 19:34:38 GMT
References: <6293@hubcap.clemson.edu>
Organization: AT&T Bell Laboratories
Lines: 26

From article <6293@hubcap.clemson.edu>, by mikeoro@hubcap.clemson.edu (Michael K O'Rourke):
> if more than one packet is received, then it only
> queues up a NM task upon the first receive while in the background.
...
> Is it all right to queue up a NM task (one that blinks icon, beeps, and 
> places mark in apple menu) and yet have the program continue to run 
> until the user chooses to bring to foreground? Right now, when it gets its
> first packet while in background, it queues up NM task fine.  But when it get
> the next packet in background it either locks or the program comes to
> foreground for a second and then goes back the background.  This does NOT
> happen if i turn the Not. Man. option off...

There's no problem continuing to run with a NM task queued.  However, 
given all the rest, I'd question your assertion that you only queue the
NM task once.  I'm REAL careful to not queue the second task a second time.

Also, under what circumstances do you enqueue the NM task?  Remember
that AppleTalk listeners, completion routines, etc., operate at interrupt
time, with all the restrictions that apply to such routines.  Best policy
is to simply "make a note" (you'll need SetUpA5()/RestoreA5() in the
completion routine) that notification is necessary, then queue the NM task
from your main event loop.

Hope that helps...

=Ned Horvath=