Defining: proxy generation time and execution time. In generation time you can have access to a selector, that's why I added to options. It was intended to drive the methods that would be proxy, even to skip the ones that wouldn't.
When I was planning the implementation of this, I realized how this could be problematic for simple windsor scenarios. So I gave up implementing the selector at all. I can't remember all the reasons, but it should come once you consider all aspects: - proxying a type for the first time (scenario 1) - re-proxying a type for different scenario (logging + atm) - new container on same appdomain, reproxying - serialization/deserialization of proxy Actually, I cant remember why serialization is important to us. It is certainly a source of big problems.. NHibernate maybe? I'd encourage the team to find out why and possibly drop this feature. On leaking this.. Since DP1 I havent heard any complaint for not supporting this, so I wouldnt add this. It impacts on performance and has no real benefits. On Tue, Dec 16, 2008 at 7:59 AM, Fabian Schmied <[email protected]> wrote: > >> You can't do that. >> Simple reason is, that you don't get access to interceptors while generating >> proxy type, ergo you can't call selector on them, ergo it has to be done at >> runtime. > > Hm, that's true. Let's see what Hammett says. > > Fabian > > > > -- Cheers, hammett http://hammett.castleproject.org/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Castle Project Development List" 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-devel?hl=en -~----------~----~----~----~------~----~------~--~---
