tag:blogger.com,1999:blog-7005051.post109623644372352707..comments2004-09-29T23:01:50.423+02:00Comments on Fast-Forward ยป: Multicast eventsOndrej Kellehttp://www.blogger.com/profile/11973677794354930454noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-7005051.post-1096282906605124322004-09-27T13:01:00.000+02:002004-09-27T13:01:00.000+02:00I'm fairly certain the multicast event handlers in...I'm fairly certain the multicast event handlers in .NET are called in an indeterminate order which is one of the main reasons I find them unattractive.LachlanGhttps://www.blogger.com/profile/05666168623106775966noreply@blogger.comtag:blogger.com,1999:blog-7005051.post-1096267088920302202004-09-27T08:38:00.000+02:002004-09-27T08:38:00.000+02:00Thanks for your comment! In my opinion, multicast ...Thanks for your comment! In my opinion, multicast events don't make debugging much more complicated: the main difference is that the source object holds a list of method pointers instead of a direct link; when the time comes to fire an event, it will simply iterate the list and call each target handler.Ondrej Kellehttps://www.blogger.com/profile/11973677794354930454noreply@blogger.comtag:blogger.com,1999:blog-7005051.post-1096259029698352812004-09-27T06:23:00.000+02:002004-09-27T06:23:00.000+02:00Personally I'm a bit hesitant about multicast even...Personally I'm a bit hesitant about multicast events. I'm yet to use them in a proper project but I don't like the idea of what would be a single easy to follow unicast event handler being changed into multiple handlers with unpredictable quasi-thread-like behaviour. Sounds like a recipe for future hair pulling debugging sessions and a more difficult flow of execution for others to follow when LachlanGhttps://www.blogger.com/profile/05666168623106775966noreply@blogger.com