 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
.NET Forum / .NET Framework / Component Services / January 2004COM+ contexts
Hello. I need some help in order to understand contexts. The article at http://www.gotdotnet.com/team/xmlentsvcs/espaper.aspx says that a context is an environment for objects with similar execution requirements. If I have two serviced components with exactly the same attibutes defined, will they have the same context? Is this context generated for components at the same COM+ application or can components in different COM+ applications have the same context? Sorry, but the MS docs seems rather confusing for newbies, I think. Thanks, Robert Scheer Hi Robert, > I need some help in order to understand contexts. The article at > http://www.gotdotnet.com/team/xmlentsvcs/espaper.aspx says that a > context is an environment for objects with similar execution > requirements. If I have two serviced components with exactly the same > attibutes defined, will they have the same context? Nope, not necessarily. Some attribute values for creation of the object on a new context. Also notice that when one says that the components might share the same context, that's not exactly true. Rather, object instances might share the same context if the attributes allow it AND they are created in the same execution line (that is, if they are not created during the same calling stack, invocation or whatever you want to call it, they won't share context). > Is this context > generated for components at the same COM+ application or can > components in different COM+ applications have the same context? Context is an in-process structure. It can be shared by two components in different applications IF they are created inside the same process (so for example, a server and a library app would do).  SignatureTomas Restrepo tomasr@mvps.org Hi Robert, > I need some help in order to understand contexts. The article at > http://www.gotdotnet.com/team/xmlentsvcs/espaper.aspx says that a > context is an environment for objects with similar execution > requirements. If I have two serviced components with exactly the same > attibutes defined, will they have the same context? Nope, not necessarily. Some attribute values for creation of the object on a new context. Also notice that when one says that the components might share the same context, that's not exactly true. Rather, object instances might share the same context if the attributes allow it AND they are created in the same execution line (that is, if they are not created during the same calling stack, invocation or whatever you want to call it, they won't share context). * > Is this context > generated for components at the same COM+ application or can > components in different COM+ applications have the same context? Context is an in-process structure. It can be shared by two components in different applications IF they are created inside the same process (so for example, a server and a library app would do). * I guess I'm not sure how to express it nicely without bringin in some extra COM+ concepts that would make it somewhat complicated... You should definitely pick up a copy of Tim Ewald's "Transactional COM+" book, since it explains all this in very much detail. SignatureTomas Restrepo tomasr@mvps.org
Free MagazinesGet these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...
|
Reply to this Message
|
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.