> If you're guaranteed that you'll always be crossing a remoting > boundary, you can do a "poor-man's" interception.
I've had a couple of inquiries about this technique. As a result, I've posted a sample to GotDotNet [1]. This sample demonstrates remote method interception at a target object by simply implementing IMessageSink in a base class of the target object. Upon receiving a synchronous message, the base class uses reflection on itself (and its derived classes) to dispatch the actual method call. Again, this technique only works if the method call crosses a remoting boundary. As always, the sample is given "as is". Your actual mileage may vary... Have fun, Jim [1] http://www.gotdotnet.com/userarea/filedetails.aspx?FileName=MessageSinkInter ception.zip You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
