Is it possible to proxy my accessors for AOP types of behavior?  I have two problems when I look at this.  One, I will need some means to control the creation process by NetKernel and second, the lack of interfaces at this level.  I realize I could probabaly implement my own base accessor and in turn achieve some of the same goals but I like the idea of wrapping them post implementation.

I also realize there will be overlay opportunites in 4.x but we are currently working in 3 and will be there for a while.  In either case wrapping the accessor would work in both platforms.

Hi Shane,

Because of the loose coupling inherent in ROC, adding AOP-like behavior is easy. It is most often a matter of "wrapping" existing services by intercepting or translating their logical addresses.

So, instead of thinking about extending accessors or altering code, imagine the logical requests flowing around the system. The logical requests are all specified by URIs. You probably want to "intercept" only a identified subset of these URIs and pass the rest through. This is the ROC equivalent of identifying your joinpoints in AOP.

You are correct in identifying this pattern as an overlay in NK4, but the Functional Overlay pattern is also implementable in NK3:

http://docs.1060.org/docs/3.3.0/book/architectguide/doc_tutorial_patterns_functional_overlay.html

     regards,
     -Tom
[/quote]