DOC: spoe: Clarify use of the event directive in spoe-message section

Only one event is possible for a spoe-message section. If defined several
time, only the last one is considered. The documentation is now explicit on
this point.

This patch is related to the the issue #1351.

(cherry picked from commit d322e948c979cff5bd419aa1b716186615651ba1)
Signed-off-by: Christopher Faulet <cfaulet@haproxy.com>
(cherry picked from commit 75a81ef8cacd5444615197980b1c774bd57dd8af)
Signed-off-by: Christopher Faulet <cfaulet@haproxy.com>
(cherry picked from commit dadbbae0e7754791adca350f0dd4a64aabd8c78c)
Signed-off-by: Willy Tarreau <w@1wt.eu>

diff --git a/doc/SPOE.txt b/doc/SPOE.txt
index 71c7fde..2843308 100644 (file)
--- a/doc/SPOE.txt
+++ b/doc/SPOE.txt
@@ -509,7 +509,8 @@ args [name=]<sample> ...
 event <name> [ { if | unless } <condition> ]
   Set the event that triggers sending of the message. It may optionally be
   followed by an ACL-based condition, in which case it will only be evaluated
-  if the condition is true.
+  if the condition is true. A SPOE message can only be sent on one event. If
+  several events are defined, only the last one is considered.
 
   ACL-based conditions are executed in the context of the stream that handle
   the client and the server connections.