Willy Tarreau b5281283bb MINOR: task: define two new one-shot events for use with WOKEN_OTHER or MSG ... TASK_WOKEN_MSG only says "someone sent you a message" but doesn't convey any info about the message. TASK_WOKEN_OTHER says "you're woken for another reason" but doesn't tell which one. Most often they're used as-is by the task handlers to report very specific situations. For some important control notifications, having the ability to modulate the message a little bit is useful, so let's define two user event types UEVT1 and UEVT2 to be used in conjunction with TASK_WOKEN_MSG or _OTHER so that the application can know that a specific condition was explicitly requested. It will be used this way: task_wakeup(s->task, TASK_WOKEN_MSG | TASK_F_UEVT1); or: task_wakeup(s->task, TASK_WOKEN_OTHER | TASK_F_UEVT2); Since events are cumulative, keep in mind not to consider a 3rd value as the combination of EVT1+EVT2; these really mean that the two events appeared (though in unspecified order).		2024-09-27 11:56:10 +02:00
..
haproxy	MINOR: task: define two new one-shot events for use with WOKEN_OTHER or MSG	2024-09-27 11:56:10 +02:00
import	BUILD: cebtree: silence a bogus gcc warning on impossible code paths	2024-09-18 17:42:52 +02:00
make	BUILD: makefile: support USE_xxx=0 as well	2024-04-11 11:06:19 +02:00