The transparent proxy obviously doesn't know anything, but it's on the client side. I'm hooking into the remoting mechanism on the server side. Adding a member to the interface is not a good solution, because I don't have an instance I can use call (if I had an instance, calling its GetType method would give me what I need...).
Anyway, what I actually need is access to attributes defined in the server's concrete class. These attributes define some server specific behavior, and are a very natural solution to the problem at hand (I use the attributes to describe syncrhonization between different instances of the same class - Liskov can relax). Thanks, Itay. -----Original Message----- From: Ron Inbar [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 25, 2006 8:32 AM To: ADVANCED-DOTNET@DISCUSS.DEVELOP.COM; Itay Zandbank Subject: Re: A Server Side Sink Problem You don't necessarily have that information. The Transparent Proxy may be created from the interface definition alone, without having any knowledge about the concrete object. Anyway, you seem to be in violation of Liskov's Substitution Principle. You may want to add a member to the interface that provides you with exactly the information you need, instead of relying on knowing the concrete type. Ron =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
