HighTechTalks DotNet Forums  

Thoughts on ServicedComponents and the Construct() method?

Dotnet Framework (Component Services) microsoft.public.dotnet.framework.component_services


Discuss Thoughts on ServicedComponents and the Construct() method? in the Dotnet Framework (Component Services) forum.



Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old   
Jim Bancroft
 
Posts: n/a

Default Thoughts on ServicedComponents and the Construct() method? - 11-17-2004 , 11:08 AM







Hi everyone,

I'm creating a serviced component in C#, and was thinking about calling
the Construct() method to cache a string in a local variable, for later use.
In VB6 I had it burned into me that caching values in a COM+ component
wasn't maybe the best idea, given how COM+ and JIT worked. I was told that
with JIT you're not guaranteed to use the same component between method
calls, so trying to hold state in a variable is asking for trouble.

Was that line of reasoning correct, and if so, does it hold in .Net as
well, and should I avoid caching a string in the Construct method because of
it? Thanks,

-Jim



Reply With Quote
Reply




Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

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

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.4
Copyright ©2000 - 2013, Jelsoft Enterprises Ltd.