Only if your context data object implements ILogicalThreadAffinative. Also note that in some cases (remoting to an out of appdomain object), your ILogicalThreadAffinative data in CallContext can be destroyed (removed from the CallContext) if an error occurs in the remoting framework. This isn't very likely to happen, but it hit me once and I had to work around it (I was assuming that the data in CallContext would be there after a remoting call, so I only ever set the data once; you need to set the data every call to make sure it's there).
Adam.. > -----Original Message----- > From: Unmoderated discussion of advanced .NET topics. > [mailto:[EMAIL PROTECTED] On Behalf Of Roni Burd > Sent: Friday, April 01, 2005 12:11 PM > To: [email protected] > Subject: Re: [ADVANCED-DOTNET] ThreadLocal storage > > Thanks for the replies. What I didn't want was to use > System.Web so I created my own Context using CallContext > (similar to what HTTPContext does). > > > What I don't know is does CallContext travel if I call a COM+ > (ServicedComponent) object? =================================== This list is hosted by DevelopMentor� http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
