<?xml version="1.0"?>
<rss version="2.0">
<channel>
  <title>Simon Brown - aspects tag</title>
  <link>http://www.simongbrown.com/blog/tags/aspects/</link>
  <description>Coding the architecture</description>
  <language>en</language>
  <copyright>Simon Brown</copyright>
  <lastBuildDate>Tue, 06 May 2008 13:33:00 GMT</lastBuildDate>
  <generator>Pebble (http://pebble.sourceforge.net)</generator>
  <docs>http://backend.userland.com/rss</docs>
  
  
  <item>
    <title>Thinking in aspects</title>
    <link>http://www.simongbrown.com/blog/2008/02/12/thinking_in_aspects.html</link>
    
      
        <description>
          &lt;p&gt;
AOP has proven itself as a very useful technique for centralising the cross-cutting concerns of an application and many of us use aspects in our day to day work, but are people thinking in aspects yet?
&lt;/p&gt;

&lt;p&gt;
For example, frameworks like Spring use aspects under the covers to implement things like support for transactions, but effectively this is all hidden away from the developer. What I&#039;m interested to know is whether people are explicitly designing aspects into their software. Based upon my own experience, I&#039;ve not seen many instances where this has been done; where developers have made a concious decision to use aspects to solve a particular problem. Are your experiences the same?
&lt;/p&gt;
        </description>
      
      
    
    
    
    <category>Java</category>
    
    <comments>http://www.simongbrown.com/blog/2008/02/12/thinking_in_aspects.html#comments</comments>
    <guid isPermaLink="true">http://www.simongbrown.com/blog/2008/02/12/thinking_in_aspects.html</guid>
    <pubDate>Tue, 12 Feb 2008 12:21:00 GMT</pubDate>
  </item>
  
  </channel>
</rss>
