PC Review


Reply
Thread Tools Rate Thread

CallContext behavior

 
 
A Rothberg
Guest
Posts: n/a
 
      28th Jul 2004
Have some questions about the behavior of CallContext and visibility
to the CallContext data.

Can someone please confirm (or deny) that the observed behaviors are
by design and will not be changing in future releases of .NET

Given a caller that sets data in CallContext via SetData()...
If the callee is a:

Remoted Singleton - The caller's CallContext data is available,
changes made to CallContext are visible to the caller

Async Delegate - The caller's CallContext data is available, changes
made to CallContext are NOT visible to the caller

new Thread - The caller's CallContext data is not available

Method Call (to another class) - The caller's CallContext data is
available, changes made to CallContext are visible to the caller


Thanks.
 
Reply With Quote
 
 
 
Reply

Thread Tools
Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Threads and CallContext problems =?Utf-8?B?VHJveQ==?= Microsoft Dot NET Framework 0 15th Aug 2006 01:00 PM
CallContext thread safe Tommaso Caldarola Microsoft C# .NET 1 11th May 2006 05:38 PM
Remoting, CallContext, NLB Hawix Microsoft Dot NET Framework 1 7th Oct 2005 10:48 AM
CallContext and unloading AppDomain Michael Per Microsoft Dot NET Framework 0 2nd Aug 2005 06:18 PM
Using CallContext For Request-Specific Storage Pham Nguyen Microsoft ASP .NET 5 9th Mar 2005 01:26 AM


Features
 

Advertising
 

Newsgroups
 


All times are GMT +1. The time now is 05:13 PM.