This whole "aspect-oriented" thing doesnt do anything that wasnt done before. There are many OO patterns that do the same job and dont incur the overhead of having a Java (!) extension. MVC (Model-View-Controller, http://c2.com/cgi/wiki?ModelViewController) separates the controller (which handles which "GotoPage" method to use), the view which handles all the presentation, the templating, etc. and the model, that actually does the logic part. Couple that with the intercepting filter pattern (basically, a chain of responsibility), which has the controller and an authenticate filter, and one filter per aspect, and you have a well-designed, reusable OO solution to the aspect problem.
Aspect-oriented is just another word for layering, and layering has been the choice for software architecture for a long time.
Slashdot Mirror
Or are you suggesting to handle data mirroring across 5000 servers ? That seems easier...
This whole "aspect-oriented" thing doesnt do anything that wasnt done before. There are many OO patterns that do the same job and dont incur the overhead of having a Java (!) extension. MVC (Model-View-Controller, http://c2.com/cgi/wiki?ModelViewController) separates the controller (which handles which "GotoPage" method to use), the view which handles all the presentation, the templating, etc. and the model, that actually does the logic part. Couple that with the intercepting filter pattern (basically, a chain of responsibility), which has the controller and an authenticate filter, and one filter per aspect, and you have a well-designed, reusable OO solution to the aspect problem. Aspect-oriented is just another word for layering, and layering has been the choice for software architecture for a long time.