http://ayende.comAyende @ RahienCopyright (C) Ayende Rahien 2004 - 2021 (c) 202660No, 3.5 doesn't address that, a huge pity. http://ayende.com/2432/event-broker-spiking#comment13http://ayende.com/2432/event-broker-spiking#comment13Sat, 26 May 2007 10:37:56 GMTAhh, wasn't aware of the implemenation. Good to know. And 3.5 doesn't address this? Pity. http://ayende.com/2432/event-broker-spiking#comment12http://ayende.com/2432/event-broker-spiking#comment12Sat, 26 May 2007 04:00:55 GMTActually, I meant the business concerns in the sample itself is not a good example. About strings, that is an issue that I have to take with the CLR team. Attributes can accept a limited number of parameter types. Basically int, long, string and System.Type. This limits the ability to do anything _really_ interesting with attributes. http://ayende.com/2432/event-broker-spiking#comment11http://ayende.com/2432/event-broker-spiking#comment11Fri, 25 May 2007 22:16:07 GMTTwo things I"m curious about. First, why do you say the last example (CustomerAdded event) is a bad example? Second, if you don't like string equality then why not use real objects, much like how Rhino does mocking (way better than how NMock2 did wtih it's string method and object names). I mean, if you're setting out to build a similar mousetrap that's simpler then the CAB implementation, why not build a better one for the same cost (okay, using objects and maybe reflection is n+ more effort than comparing strings, but I don't think it's a huge effort is it?) http://ayende.com/2432/event-broker-spiking#comment10http://ayende.com/2432/event-broker-spiking#comment10Fri, 25 May 2007 22:02:41 GMTAh, cool. That's more Event bus really. The event bus catches the events and dispatches it using some interesting logic, and possibly filters. Very useful for desktop applications! http://ayende.com/2432/event-broker-spiking#comment9http://ayende.com/2432/event-broker-spiking#comment9Fri, 25 May 2007 18:40:55 GMTIs it different from the Castle's event wiring facility? http://ayende.com/2432/event-broker-spiking#comment8http://ayende.com/2432/event-broker-spiking#comment8Fri, 25 May 2007 18:25:17 GMTThis is basically an event registry, you can register to an event, and something else can invoke it. The idea is that I can register to "Customer-Added" event, and someone else can raise it. This is limited to a single app model, since the underlying model is .Net events, basically. http://ayende.com/2432/event-broker-spiking#comment7http://ayende.com/2432/event-broker-spiking#comment7Fri, 25 May 2007 18:24:38 GMTI'm not familiar with event brokers. Is this something similar to the Event Bus pattern? http://ayende.com/2432/event-broker-spiking#comment6http://ayende.com/2432/event-broker-spiking#comment6Fri, 25 May 2007 18:20:31 GMTI've implemented an Event Broker in a messaging add-in for Titan as well, which also uses string identifiers for channels. Since the rest of Titan is much more intelligent than that, I'm interested in anyone's ideas to alternatives. The real difficulty is that I want to be able to set up the pubs and subs declaratively via attributes, and you can't get much more intelligence in attributes other than constants... http://ayende.com/2432/event-broker-spiking#comment5http://ayende.com/2432/event-broker-spiking#comment5Fri, 25 May 2007 13:44:54 GMTFun is always high on my checklist when building software, so have at it. I still don't see how CAB is intrusive so it'll be interesting to compare your end result with CAB (specifically around the pieces you implemented only) to see how intrusive either is. I personally don't see the intrusion myself. http://ayende.com/2432/event-broker-spiking#comment4http://ayende.com/2432/event-broker-spiking#comment4Fri, 25 May 2007 12:32:46 GMT> the point of this exercise? I, at least, am having fun. There isn't much to it otherwise. I am saying that the CAB has a lot of good idea, but I don't like the direction that it takes. This is different than saying that I don't like the implementation. Implementation == code, direction == overall design goals of the system. IMO, the CAB has a too intrusive approach, which makes things a lot harder to deal with for the end user. http://ayende.com/2432/event-broker-spiking#comment3http://ayende.com/2432/event-broker-spiking#comment3Fri, 25 May 2007 10:00:52 GMTIt's interesting. Between you and Jeremy, you'll single handly build a version of CAB but is this really the point of this excercise? Is the issue is that CAB is large and unweildly and the guys that follow what P&P is pushing should look towards more lean and mean implmentations like this? Are you guys saying that the current CAB is good in concept but poor in implemenation. Just trying to figure out the intentions behind these excercises. http://ayende.com/2432/event-broker-spiking#comment2http://ayende.com/2432/event-broker-spiking#comment2Fri, 25 May 2007 05:12:28 GMTooh, can't wait for this one - would love to get your perspectives on it :-). Chris http://ayende.com/2432/event-broker-spiking#comment1http://ayende.com/2432/event-broker-spiking#comment1Fri, 25 May 2007 04:11:51 GMT