David Newton wrote:I don't see any relation at all; could you elaborate on how they're similar? Thanks!
Perhaps in the sense that the rules and actions are "around" the events, versus the actual events themselves. You have various observers keyed to the lifecycle of the event and execute logic upon those, rather than necessarily specifically on the event.
The events are "ignorant" of the logic, the processing system is firing logic as the events go by.
In a similar manner, but perhaps reversed manner, in AOP the logic is ignorant of the aspects. AOP is all about instrumenting the runtime to get your aspect logic injected in to the function call flow of the application, much like event processing is based on the event flow.
Perhaps it's a reach, but in the right light, you can perhaps see how they're similar.
Yeah, I realized after posting that there's a lot of around and processing chains that are AOP-like; I didn't get around to following up. Thanks!
Joined: Aug 04, 2010
The principle in event processing is that there are "event producers", "event consumers" and "event processing agents". There is a separation principle here, in the sense that they are independent - an event producer does not know what processing is done with the events it produces, and an event processing agent is totally independent both from the producer and consumer. This total independence of each component has some similarity to the idea of AOP
subject: Has "Event Process in Action" something to do with AOP (Aspect Oriented Programming)?