you're not the first person to request this :) However due to limitations of your approach, you could easily end up with state corruption, where part of the state comes from proxy, part of it comes from the target which can lead to all sorts of nasty issues.
Why do you need that? There's a feature planned for v3 called Type Wrapping, targetter at WPF scenarios (among others) - take a look: http://using.castleproject.org/display/CASTLE/Dynamic+Proxy+3+design+meeting W dniu 15 września 2009 16:24 użytkownik José F. Romaniello <[email protected]> napisał: > > mmm, I understood. > > I would like to have something like "class proxy with target", but > probabily I've a design concept issue in my mind. > > > > > On 15 sep, 02:58, Krzysztof Koźmic <[email protected]> wrote: >> because for ClassProxy, the proxy type inherits from the proxied >> class. That is to have one instance to call to both members - these >> proxable, and these nonproxyable, among other things. >> >> 2009/9/15 José F. Romaniello <[email protected]>: >> >> >> >> > Sorry, this is a newbie question about the design of DP. >> > Why a ClassProxy doesn't have target? > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Castle Project Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/castle-project-users?hl=en -~----------~----~----~----~------~----~------~--~---
