[Mono-devel-list] Repost: Question: Using the CallContext class from a custom channel sink.

Lluis Sanchez lluis at ximian.com
Thu Nov 18 05:01:21 EST 2004

On dc, 2004-11-17 at 09:12 -0500, Sébastien Robitaille wrote:
> ...
> I had a quick look at mono source code and I think that this problem may be related to the way mono handles LogicalCallContexts (as
> I understand, RemotingServices.InternalExecuteMessage temporary replaces the CallContext data by the LogicalCallContext instead of
> "appending it" to the actual content. This may be the cause of this behavior).

Yes, InternalExecute replaces the current context with the data from the
request message. If MS.NET behaves in a different way this might be a
bug. Can you file a bug report in bugzilla.ximian.com with a simple test


> Anyway, I already found a workaround (by directly using a Thread data slot instead of the CallContext class), but I was curious if
> this is a bug or if I was using the CallContext class incorrectly.
> Thanks for your help.
> Sébas
> _______________________________________________
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list

More information about the Mono-devel-list mailing list