Introducing: .NET Event Cache

Sign in to leave a comment.

• A

  Allan17y agoPosted Mar 16, 2009, 9:57 AM

  WTF are you talking about? Bubbling who? And what does this mean: "This article introduces a reusable generic event cache component that houses events with custom bubbling capabilities. This can be used as a component in your business objects to provide event declaration runtime with events that can bubble to other classes. " Did you make that up? Wow. Program for over 10 years, think you've seen it all...
  • MC

    Matthew Cochran17y agoPosted Mar 16, 2009, 9:11 PM

    I’m not sure exactly what the point(s) of confusion are, but I’m hoping the following can help clarify things: Event Bubbling (ASP.NET): http://msdn.microsoft.com/en-us/library/aa719644(VS.71).aspx I’m encapsulating and this pattern and expanding some of the functionality for reuse on the business logic tier. The idea is that parts of the functionality can then be exposed by domain level classes via composition (http://www.artima.com/designtechniques/compoinh.html) from reusable component(s) (http://en.wikipedia.org/wiki/Reusable_software_components) . What I mean by a “cache” is that there are objects held in memory that are used to hold references to the event wiring. This pool of objects (the cache) is accessed through a façade. The API can be consumed in a generic manner (using .NET Generics). The code samples in the article demonstrate this. http://msdn.microsoft.com/en-us/library/ms379564(VS.80).aspx Exposing new events and consuming them can be done runtime in addition to compile time. Hope this helps, -Matt