Comments on: Using AOP to manage multiple products from one base http://almaer.com/blog/using-aop-to-manage-multiple-products-from-one-base blogging about life, the universe, and everything tech Sat, 08 Sep 2012 07:06:53 -0700 http://wordpress.org/?v=2.8.4 hourly 1 By: Dion http://almaer.com/blog/using-aop-to-manage-multiple-products-from-one-base/comment-page-1#comment-23045 Dion Mon, 02 May 2005 19:21:18 +0000 http://almaer.com/blog2/using-aop-to-manage-multiple-products-from-one-base#comment-23045 Emmanuel: There are definitely issues with cracking, and plugins make total sense. AOP can give you the power in the few cases where plugins are not enough, as it gives you infinite extension points. I think the 'm' bug is fixed now. MT-Blacklist added 'm...' which meant m followed by 3 characters! Cheers, Dion Emmanuel:

There are definitely issues with cracking, and plugins make total sense. AOP can give you the power in the few cases where plugins are not enough, as it gives you infinite extension points.

I think the ‘m’ bug is fixed now. MT-Blacklist added ‘m…’ which meant m followed by 3 characters!

Cheers,

Dion

]]> By: E??anuel Pirsch http://almaer.com/blog/using-aop-to-manage-multiple-products-from-one-base/comment-page-1#comment-23044 E??anuel Pirsch Mon, 02 May 2005 19:01:06 +0000 http://almaer.com/blog2/using-aop-to-manage-multiple-products-from-one-base#comment-23044 The idea is ok but has drawbacks... If you centralize, in aspetcs, your "crippling" features, they are a lot easier to disable. Unless you use co?pile ti?e weaving, but then you cannot easily uncripple the product with an activation key. I also think that a plugin architecture is a lot better way to create a product that can packaged in several editions... Because a plugin architecture uses extention points, it is a lot cleaner (for the product developper) to work with than with aspects that can do whatever they want wherever they want. AOP can be use to ?ake an existing product available (by weaving in extension points) in ?any editions a bit easier. We ?ust not forget that AOP has been invented to address cross-cuttong concerns. I don't think bundling a product with features X and Y re?oved is a cross-cutting concern. (note: replace ? with the letter after 'l' - the content filter don't like that letter) The idea is ok but has drawbacks… If you centralize, in aspetcs, your “crippling” features, they are a lot easier to disable. Unless you use co?pile ti?e weaving, but then you cannot easily uncripple the product with an activation key.

I also think that a plugin architecture is a lot better way to create a product that can packaged in several editions… Because a plugin architecture uses extention points, it is a lot cleaner (for the product developper) to work with than with aspects that can do whatever they want wherever they want.

AOP can be use to ?ake an existing product available (by weaving in extension points) in ?any editions a bit easier.

We ?ust not forget that AOP has been invented to address cross-cuttong concerns. I don’t think bundling a product with features X and Y re?oved is a cross-cutting concern.

(note: replace ? with the letter after ‘l’ – the content filter don’t like that letter)

]]>