Comments on: Eureka! AOP is the final piece of the multi-threaded smart client puzzle http://www.udidahan.com/2007/12/07/eureka-aop-is-the-final-piece-of-the-multi-threaded-smart-client-puzzle/ Enterprise Development Expert & SOA Specialist Sun, 14 Mar 2010 06:27:00 -0500 http://wordpress.org/?v=2.8.4 hourly 1 By: udidahan http://www.udidahan.com/2007/12/07/eureka-aop-is-the-final-piece-of-the-multi-threaded-smart-client-puzzle/comment-page-1/#comment-25246 udidahan Wed, 18 Jun 2008 20:50:33 +0000 http://udidahan.weblogs.us/2007/12/07/eureka-aop-is-the-final-piece-of-the-multi-threaded-smart-client-puzzle/#comment-25246 Nick, Proving (and maintaining) the immutability of an object graph isn't trivial. Other than that, yes, you're right. Nick,

Proving (and maintaining) the immutability of an object graph isn’t trivial. Other than that, yes, you’re right.

]]> By: Nick Guenther http://www.udidahan.com/2007/12/07/eureka-aop-is-the-final-piece-of-the-multi-threaded-smart-client-puzzle/comment-page-1/#comment-25132 Nick Guenther Tue, 17 Jun 2008 19:45:33 +0000 http://udidahan.weblogs.us/2007/12/07/eureka-aop-is-the-final-piece-of-the-multi-threaded-smart-client-puzzle/#comment-25132 Why don't you just use immutable objects everywhere? You pay a memory cost in order to guarantee thread safety (in fact, thread safety becomes a non-issue then). Why don’t you just use immutable objects everywhere? You pay a memory cost in order to guarantee thread safety (in fact, thread safety becomes a non-issue then).

]]> By: What Makes Smart Clients Safe? http://www.udidahan.com/2007/12/07/eureka-aop-is-the-final-piece-of-the-multi-threaded-smart-client-puzzle/comment-page-1/#comment-13006 What Makes Smart Clients Safe? Wed, 26 Dec 2007 09:21:54 +0000 http://udidahan.weblogs.us/2007/12/07/eureka-aop-is-the-final-piece-of-the-multi-threaded-smart-client-puzzle/#comment-13006 [...] my recent post on using AOP for smart client development, my partner-in-crime, Arnon, suggested I explain a little [...] [...] my recent post on using AOP for smart client development, my partner-in-crime, Arnon, suggested I explain a little [...]

]]> By: thesoftwaresimplist http://www.udidahan.com/2007/12/07/eureka-aop-is-the-final-piece-of-the-multi-threaded-smart-client-puzzle/comment-page-1/#comment-12193 thesoftwaresimplist Sun, 09 Dec 2007 18:53:55 +0000 http://udidahan.weblogs.us/2007/12/07/eureka-aop-is-the-final-piece-of-the-multi-threaded-smart-client-puzzle/#comment-12193 Casey, I see. I'm not looking for the ultimate AOP solution here. On the contrary. I'm looking for something simple that will work under "messy" conditions - a new module needs to be integrated that was developed by another company - only DLLs available, no source to compile myself. Also, if a developer compiled some code on their machine and put out a quick fix to a bug, without going through that post-compilation step, I wouldn't want that to destabilize the system. Thanks for the heads-up, though. It is always good to have another tool in my toolbelt. Casey,

I see. I’m not looking for the ultimate AOP solution here. On the contrary. I’m looking for something simple that will work under “messy” conditions – a new module needs to be integrated that was developed by another company – only DLLs available, no source to compile myself. Also, if a developer compiled some code on their machine and put out a quick fix to a bug, without going through that post-compilation step, I wouldn’t want that to destabilize the system.

Thanks for the heads-up, though. It is always good to have another tool in my toolbelt.

]]> By: Casey http://www.udidahan.com/2007/12/07/eureka-aop-is-the-final-piece-of-the-multi-threaded-smart-client-puzzle/comment-page-1/#comment-12171 Casey Sun, 09 Dec 2007 09:11:36 +0000 http://udidahan.weblogs.us/2007/12/07/eureka-aop-is-the-final-piece-of-the-multi-threaded-smart-client-puzzle/#comment-12171 Well from reading here: http://blog.bittercoder.com/CategoryView,category,PostSharp.aspx Postsharp also allows AOP on internal or sealed types, I believe that ASpect# also requires virtual methods. I certainly understand about the visibility aspect of it - I'm very much one for clear and exposed functionality, rather than 'magic' approach ... but it is another tool in your arsenal I guess ... Well from reading here:
http://blog.bittercoder.com/CategoryView,category,PostSharp.aspx

Postsharp also allows AOP on internal or sealed types, I believe that ASpect# also requires virtual methods.

I certainly understand about the visibility aspect of it – I’m very much one for clear and exposed functionality, rather than ‘magic’ approach … but it is another tool in your arsenal I guess …

]]> By: thesoftwaresimplist http://www.udidahan.com/2007/12/07/eureka-aop-is-the-final-piece-of-the-multi-threaded-smart-client-puzzle/comment-page-1/#comment-12129 thesoftwaresimplist Sat, 08 Dec 2007 10:18:25 +0000 http://udidahan.weblogs.us/2007/12/07/eureka-aop-is-the-final-piece-of-the-multi-threaded-smart-client-puzzle/#comment-12129 Casey, Neither am I :-) I'm more focused on what I want the solution to do, rather than how it does it. If you could explain about the limitations you mentioned, I'd be most obliged. That said, after looking at PostSharp, it does seem to require compilation. What I mean by that is that if I get a DLL/module that has types which implement IView, I have no real way of knowing they're safe - without actually looking at the IL (shudder). I would prefer a solution I know is safe for any type implementing IView (something I can easily check). The solution based on the Spring-style of AOP gives me that - I think :-) Thanks for your suggestion, though! Casey,

Neither am I :-)
I’m more focused on what I want the solution to do, rather than how it does it. If you could explain about the limitations you mentioned, I’d be most obliged.

That said, after looking at PostSharp, it does seem to require compilation. What I mean by that is that if I get a DLL/module that has types which implement IView, I have no real way of knowing they’re safe – without actually looking at the IL (shudder).

I would prefer a solution I know is safe for any type implementing IView (something I can easily check). The solution based on the Spring-style of AOP gives me that – I think :-)

Thanks for your suggestion, though!

]]> By: Casey http://www.udidahan.com/2007/12/07/eureka-aop-is-the-final-piece-of-the-multi-threaded-smart-client-puzzle/comment-page-1/#comment-12121 Casey Sat, 08 Dec 2007 06:04:27 +0000 http://udidahan.weblogs.us/2007/12/07/eureka-aop-is-the-final-piece-of-the-multi-threaded-smart-client-puzzle/#comment-12121 I'm no expert on AOP ... but one thing that really impressed me was PostSharp. Spring and Aspect# all have a limitation from the way they work, that they are very evident within your code. PostSharp avoids this entirely by IL weaving the AOP stuff in at compile time. If you haven't checked it out, it may be worth writing a comparison prototype in it to see the differences with spring. I’m no expert on AOP … but one thing that really impressed me was PostSharp. Spring and Aspect# all have a limitation from the way they work, that they are very evident within your code. PostSharp avoids this entirely by IL weaving the AOP stuff in at compile time. If you haven’t checked it out, it may be worth writing a comparison prototype in it to see the differences with spring.

]]>