ADC Home > Reference Library > Technical Notes > Legacy Documents > Networking >
Important: This document is part of the Legacy section of the ADC Reference Library. This information should not be used for new development.
Current information on this Reference Library topic can be found here:
What are network events?
When the Event Manager was designed, an event number was reserved for future
support of "network events". Later, when the AppleTalk Pascal Interfaces were
written, a completion routine was created that, when an asynchronous AppleTalk
operation finished, would post an event using
Only the AppleTalk Pascal Interfaces generate network events. Assembly-language
users of the AppleTalk drivers (and those who called the AppleTalk drivers
directly from high-level languages, using
Why not use network events?
In some cases, network events can be lost. If the Event Manager finds that the queue is full while posting an event, it discards the oldest event. In a situation (such as a server) where multiple asynchronous ATP requests may complete at once, there is a chance that events may be dropped off the end of the queue. This is more likely if the same machine is also handling user-interface events (like key presses and mouse actions).
Also, in developing improvements to our operating system, it has become apparent that to continue support of network events, we would have to compromise future enhancements to our system. So, future versions of the Macintosh operating system may ignore network events instead of passing them to the application.
How can I tell that my calls have completed without using network events?
As described on page II-275 of Inside Macintosh, you can poll the
With this technique, you can ignore any network events returned by
You may also consider using the new preferred high-level interface calls; see M.NW.AppleTalk for more information.