Apple AppleShare 3.0 File Server Controls - Manual (Page 30)

to see if the handler is interested in the event that just happened. If it
is, the server calls the handler, passing pointers to the tSEQEntry record
and a server event record owned by the server. It is up to the event handler
to copy the server event record into the application's own buffer.
The server event record contains, among other things, the following
information:
- which server event occurred
- the time of the server event (in standard Macintosh date/time form)
- any error associated with the call
- the size of the data in the next buffer
- a buffer containing the AFP packet, SCParamBlockRec, HParamBlockRec, or the
new server name (up to a maximum of 48 bytes)
- the name of the file or directory upon which the operation is being
performed
(if applicable)
- the AFP command
- the user's unique user name record ID (UNRecID)
- the user's user ID (SUserID)
- the user name of the user performing this operation (registered users only)
- the reference number and directory ID of the volume upon which this
operation was performed (if applicable)
- the socket address of this user (provided in the address block (AddrBlock)
format: net number:node ID:socket number)
The server event interface file, listed in Appendix B, contains detailed
comments about each field of the server event record.
Constraints
This section describes constraints that you must observe for the server event
mechamism to work properly. It is the server event handler's responsibility
to copy the desired informa-tion from the server event record into its own
pre-allocated buffers. The server event handler cannot make file system or
Memory Manager calls while inside its thread of control. Furthermore, because
it is really part of a completion routine in the file server's code, the
handler must relinquish control to the server as soon as possible. It is
useful to consider that the server event handler is dynamically linked into
one of the completion routines of the file server and is thus an extension to
it. Therefore, it is as important to minimize the time spent in the server
event handler as it is to minimize the time spent in the completion routines.
Every microsecond spent in the server event handler results in a
corresponding delay in the completion of file server client's call.
Although you can use server events only as notification that a condition has