Hi Krzysztof, The whole scenario is to have an interface proxy to an object over some message channel (wcf, message bus etc). Method/property calls would be serialized and sent over the channel and invoked at the host end. The client end is easy: I use InterfaceProxyWith*out*Target, intercept method/property calls, and send the IInvocation over the service bus (eg serialize IInvocation).
The host would deserialize the the IInvocation and somehow dispatch the method/property call to a target object. A workaround is to obviously Reflection Invoke the method on the target object and pass in the parameters, but I'm wondering if I can leverage any part of DynamicProxy to do it to overcome the limitations (eg performance) of Invoke? Effectively I'd like to *replace *the following host code snippet: object target; // host target object IInvocation invocation; // deserialized invocation received over message bus etc invocation.ReturnValue = invocation.Method.Invoke(target, invocation.Arguments); I hope that clarifies! Cheers, Rob -- You received this message because you are subscribed to the Google Groups "Castle Project Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/castle-project-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
