<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Fri, May 31, 2013 at 7:19 AM, Bogdan Marinescu <span dir="ltr"><<a href="mailto:bogdan.a.marinescu@intel.com" target="_blank">bogdan.a.marinescu@intel.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id=":2a" style="overflow:hidden">Add more arguments to an "addhandler" command. Each argument (after the<br>
first one, which is the name of the handler) is the name of an event class<br>
that the handler wants to be notified on. "*" is a shortcut for "listen<br>
to all events". This changes the current behaviour of bitbake, which is<br>
to broadcast all events to all listeners; instead, only the handlers<br>
that registered themselves to an event with "addhandler" will receive<br>
that event. This should improve performance, although only performance<br>
measurements will be confirm or deny this claim.<br>
This is part of the fix for YOCTO #3812, but implements filtering only<br>
for class event handlers; the other part (events filter for UIs) will be<br>
the subject of a different patch.<br>
<br>
Signed-off-by: Bogdan Marinescu <<a href="mailto:bogdan.a.marinescu@intel.com">bogdan.a.marinescu@intel.com</a>></div></blockquote></div><br>Wouldn't it be simpler, as well as less invasive to the file format, to add an 'event' or 'events' flag to the handler which indicates what events it wishes to handle?<br>
-- <br>Christopher Larson</div></div>