summaryrefslogtreecommitdiffstats
path: root/doc/user
diff options
context:
space:
mode:
authorJoel Sherrill <joel.sherrill@OARcorp.com>1998-08-13 18:18:18 +0000
committerJoel Sherrill <joel.sherrill@OARcorp.com>1998-08-13 18:18:18 +0000
commiteac2c4e05f03511cbe1a61af178b1bbbb89a1eed (patch)
tree3e1c310617afde0453a72c96de9cf547f4da8768 /doc/user
parent3e6d74967d4fb055689e5675604f00e4a1608e9f (diff)
downloadrtems-eac2c4e05f03511cbe1a61af178b1bbbb89a1eed.tar.bz2
Added text to clarify the queueing of multiple events.
Diffstat (limited to 'doc/user')
-rw-r--r--doc/user/event.t24
1 files changed, 12 insertions, 12 deletions
diff --git a/doc/user/event.t b/doc/user/event.t
index 325215e4b0..6eb3266373 100644
--- a/doc/user/event.t
+++ b/doc/user/event.t
@@ -43,20 +43,20 @@ manager:
@item Events do not hold or transport data.
@item Events are not queued. In other words, if an event is
-sent more than once before being received, the second and
-subsequent send operations have no effect.
+sent more than once to a task before being received, the second and
+subsequent send operations to that same task have no effect.
@end itemize
-An event set is posted when it is directed (or sent)
-to a task. A pending event is an event that has been posted but
-not received. An event condition is used to specify the events
-which the task desires to receive and the algorithm which will
-be used to determine when the request is satisfied. An event
-condition is satisfied based upon one of two algorithms which
-are selected by the user. The @code{@value{RPREFIX}EVENT_ANY} algorithm states that
-an event condition is satisfied when at least a single requested
-event is posted. The @code{@value{RPREFIX}EVENT_ALL} algorithm states that an event
-condition is satisfied when every requested event is posted.
+An event set is posted when it is directed (or sent) to a task. A
+pending event is an event that has been posted but not received. An event
+condition is used to specify the events which the task desires to receive
+and the algorithm which will be used to determine when the request is
+satisfied. An event condition is satisfied based upon one of two
+algorithms which are selected by the user. The
+@code{@value{RPREFIX}EVENT_ANY} algorithm states that an event condition
+is satisfied when at least a single requested event is posted. The
+@code{@value{RPREFIX}EVENT_ALL} algorithm states that an event condition
+is satisfied when every requested event is posted.
@subsection Building an Event Set or Condition