[Mono-dev] [PATCH] Less sharing between AppDomains

[Eyal Alaluf]

It would seem to me that if one invokes an object from another
app-domain using the same OS thread, that the current thread should be
switched as well. Otherwise, other problematic scenarios like using an
incorrect culture info, incorrect IPrincipal, etc.

-----Original Message-----
From: Mark Probst [mailto:mark.probst at gmail.com] 
Sent: Friday, April 10, 2009 7:47 PM
To: Eyal Alaluf
Cc: Paolo Molaro; mono-devel
Subject: Re: [Mono-dev] [PATCH] Less sharing between AppDomains

On Fri, Apr 10, 2009 at 6:14 PM, Eyal Alaluf <eyala at mainsoft.com> wrote:
> Isn't the thread instance specific to the app-domain?

No.

> Are there cases where one thread instance belongs to several different
app-domains?

A thread instance only belongs to one app-domain, but another
app-domain can be active in that thread.  For example, in thread A,
belonging to app-domain X, a proxy for an object in app-domain Y might
be invoked, and that method might, while Y is active, cause a
NumberFormatter to be put into thread A's instance, which is a bug.

Mark