Thanks Henkk, I have alot to learn about remoting and call contexts so bear with me please.... I guess I naively though the principle of message sinking and interception could apply to existing client contexts. Indeed, since my object derives from ContextBoundObject the infrastructure DOES allows me to "hook" into the chain by calling IContributeDynamicSink::GetDynamicSink() on my implementing object (as well as calling my IDynamicProperty.Name impl). If I understand you correctly, none of this stuff applies unless a context boundary is crossed since that is when a proxy is created.
On Mon, 29 Apr 2002 23:43:58 +0200, Henk de Koning <[EMAIL PROTECTED]> wrote: >Calls inside a context simply don't use the remoting infrastructure, so >there's nothing to intercept. > >Or did I misunderstand your question ? > >-- Henkk > >----- Original Message ----- >From: "Franklin Colbert" <[EMAIL PROTECTED]> >To: <[EMAIL PROTECTED]> >Sent: Monday, April 29, 2002 11:05 PM >Subject: [DOTNET] IDynamicMessageSink and new Context > > >> Hello, >> >> I am attempting to do interception using IDynamicMessageSink, >> IDynamicProperty and IContributeDynamicSink interfaces. My hope was that >I >> could inject my sink into the current (client) context w/out the need to >> create a new one and the accompanying overhead of cross context calls. >(My >> simple tests indicate this is expensive...) >> >> It appears that this only works if a new context is created. I can >> understand why this is not possible with static context sinks, but why can >> I not sink dynamically to the existing context in a context agile manner? >> Or maybe I'm missing something? >> >> Thanks, >> >> -FC >> >> You can read messages from the DOTNET archive, unsubscribe from DOTNET, or >> subscribe to other DevelopMentor lists at http://discuss.develop.com. >> > >You can read messages from the DOTNET archive, unsubscribe from DOTNET, or >subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
