Skip to content

Commit

Permalink
Remove stale language
Browse files Browse the repository at this point in the history
The event handler registration ordering is based on event handler names, not event handler reference IDs

Signed-off-by: Ralph Castain <rhc@pmix.org>
  • Loading branch information
rhc54 authored and jjhursey committed May 20, 2021
1 parent 1400ef5 commit ce9461c
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion Chap_API_Event.tex
Original file line number Diff line number Diff line change
Expand Up @@ -43,7 +43,7 @@ \section{Notification and Management}
%
\end{itemize}

Users can specify the callback order of a handler within its category at the time of registration. Ordering can be specified either by providing the relevant returned event handler registration ID or using event handler names, if the user specified an event handler name when registering the corresponding event. Thus, users can specify that a given handler be executed before or after another handler should both handlers appear in an event chain (the ordering is ignored if the other handler isn't included). Note that ordering does not imply immediate relationships. For example, multiple handlers registered to be serviced after event handler \textit{A} will all be executed after \textit{A}, but are not guaranteed to be executed in any particular order amongst themselves.
Users can specify the callback order of a handler within its category at the time of registration. Ordering can be specified by providing the relevant event handler names, if the user specified an event handler name when registering the corresponding event. Thus, users can specify that a given handler be executed before or after another handler should both handlers appear in an event chain (the ordering is ignored if the other handler isn't included). Note that ordering does not imply immediate relationships. For example, multiple handlers registered to be serviced after event handler \textit{A} will all be executed after \textit{A}, but are not guaranteed to be executed in any particular order amongst themselves.

In addition, one event handler can be declared as the \textit{first} handler to be executed in the chain. This handler will \textit{always} be called prior to any other handler, regardless of category, provided the incoming event matches both the specified range and event code. Only one handler can be so designated --- attempts to designate additional handlers as \textit{first} will return an error. Deregistration of the declared \textit{first} handler will re-open the position for subsequent assignment.

Expand Down

0 comments on commit ce9461c

Please sign in to comment.