Logging, validation, exception handling: that´s easy aspects to insert into an Event-Based Components design as I´ve shown in my previous post. But what about multi-threading? Or better: parallel and asynchronous processing? In this article I want to show you, how you could approach multi-core programming using aspects you insert into an existing EBC architecture. Asynchronous processing Why use multiple threads at all? It´s because you either want to hide latency, or you want to decrease latency, ......

In my previous post I described the architecture for a small application to index .TXT files. Here´s are the napkins with my design EBC diagrams so far: Currently the implementation is working in a synchronous and sequential mode. Now, today I want to move on and introduce a couple of aspects (in the AOP sense) into the design/code. I find Event-Based Component architectures very easy to extent in that regard. No special AOP tools necessary. But see for yourself… Adding a logging aspect The “Hello, ......

AOP still is pretty much a pain when living according to “traditional” object orientation. You need fancy tools or you need to do some advanced code slinging. With Event-Based Components, though, introducing aspects is a piece of cake. Actual code is freed from tackling special concerns. Rather concerns become a matter of architecture. But see for yourself. The scenario for today is file processing. I want an application which indexes .TXT files. The program should crawl a directory hierarchy, extract ......