zoukankan      html  css  js  c++  java
  • Why AOP?

    Return to Contents

    1. Why AOP?

    Consider a typical e-commerce project. This kind a project may contain lots of parts besides the core implementing, such as logging, caching, security, and so on. When doing OOP, these parts are directly inserted into the core implementing. For example, a typical method implementing may start with some logging, security checking for parameters, then check for caching, and then the main processing after all processing, maybe there will be some logging again.

    What problems will come to a project of this kind? First, logging, caching and security codes are in every method. Although we can extract these kinds of codes to separately libraries or at least separately classes and methods, but still there will be similar codes for calling them in every method. But these kinds of codes may not directly relate to the business logics, so there are bad smells. Second, in a typical development life cycle, we may focus on the core business logics first, and after the core implementing is ok, we do debugging and add logging, caching or security codes iteratively. Oh, of course, in this way, each time we must manually add these kinds of codes to every method. Each time! Every method! How crazy a thing!

    Can we prevent these bad smells? Can we separate codes to independent modules, core implementing and other related logging, caching, security like modules, develop, debug them independently, and merge them when necessary easily with little extra effort? We Can! Let’s AOP!

  • 相关阅读:
    【Java8】 @FunctionalInterface 函数式接口
    集合使用copy与mutableCopy的区别
    GCD中的dispatch_sync、dispatch_sync 分别与串行、并行队列组合执行小实验
    podspec文件介绍
    iOS系统app崩溃日志手动符号化
    webView文本长按显示英文
    深拷贝
    view向全屏延伸时的属性设置
    iOS 模拟器截屏快捷键
    mysql 优化常用语句
  • 原文地址:https://www.cnblogs.com/teddyma/p/232581.html
Copyright © 2011-2022 走看看