<br><br><div class="gmail_quote">On Wed, Mar 30, 2011 at 5:07 PM, Madovsky <span dir="ltr"><<a href="mailto:infos@madovsky.org">infos@madovsky.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
good suggestion.<br>
do you mean that multicast::event is available with mod_event_socket ?<br>
<br>
if I read wiki for mod-event_multicast<br>
--------------<br>
You get access to all of the same events that you would get with<br>
mod_event_socket and "event plain ALL".<br>
This can be both a blessing and a curse. Please take care to audit the<br>
events, as they'll be sent everywhere that the<br>
router of your subnet and the adjoining routers are configured to send<br>
multicast packets. You may wish to explicitly<br>
plan for this and use a VLAN or similar precaution to protect yourself from<br>
information leaking to places it need not go.<br>
---------------<br>
<br>
the problem is if my esl script listens all events from all nodes so it can<br>
unecessary grow the data incoming<br></blockquote><div><br></div><div>Yep. You can't have it both ways - either you have to connect to each node to send hupall via the socket or you need to listen to multicast traffic and pick out the events you wish to act upon. I suppose the third choice would be to create a "multicast event proxy" that handles the filtering of events to/from each box. </div>
<div><br></div><div>Any other suggestions out there?</div><div><br></div><div>-MC</div><div><br></div></div>