ServicesResourcesConferencesOur TeamWeblogsAboutContact
   
No IMessageSink interception for ServicedComponents

Follow up to my previous post regarding the possibility of intercepting a call to ServicedComponent by having it implement IMessageSink. Short story: it doesn't work. Reason: ServicedComponentProxy calls RemotingServices.ExecuteMessage() which basically just dumps the message onto the StackBuilderSink from where the method call will be executed directly.

Whidbey feature request: Interception capabilities for ServicedComponents. Would be pretty cool.

posted on Saturday, November 30, 2002 1:59 PM

# re: No IMessageSink interception for ServicedComponents @ Tuesday, September 12, 2006 10:05 PM

Oh my God!!!
It was exactly what I need!!!
As long as I knew, it was possible, but, you said that is not...
Do you know another way to do this?
Lucas Ottoni


Powered by Community Server, by Telligent Systems