Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!bionet!apple!oliveb!amiga!kodiak
From: kodiak@amiga.UUCP (Robert R. Burns)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Flushing handlers out of memory.
Message-ID: <4174@amiga.UUCP>
Date: 17 Jul 89 20:36:15 GMT
References: <59256@linus.UUCP> <18551@usc.edu> <4118@amiga.UUCP> <18560@usc.edu>
Reply-To: kodiak@tooter.UUCP (Robert R. Burns)
Organization: Commodore-Amiga Inc, Los Gatos CA
Lines: 13

... back to the original thread: remember that the message port (a.k.a.
dn_Task) of your handler is made available to anyone scanning the device
list or calling DeviceProc().  Although you can flush your own handler
in a development environment where you have some certainty that this port
has not been cached by some other application, flushing it in a product
is a guru pheromone.

- Kodiak
-- 
Bob Burns, amiga!kodiak				   _
	| /_  _|. _ |	   Commodore __		  |_) _ |_  _ )'
	|<(_)(_)|(_\|<	    /\ |  ||| _` /\	  |_)(_\| )(_\ |
	| \ Software	___/..\|\/|||__|/..\___		   Faith