Does private classes and BAS modules hamper scalability in COM+?

[samansh]

Does private classes and using variables in BAS modules to maintain state information between method calls hamper scalability in a COM+ application written in Visual Basic 6.0?

I understand private classes in VB don't have any CLSID and they are not SCM aware so they won't be able to utilize COM+ benefits. Should they be avoided in COM+ applications?

Using global variables to hold state information in BAS modules can provide good peformance as the data is stored in Thread Local Storage (TLS) but can this solution hamper scalability?

What is more important Scalability or Performance?

Please help.

 

[vickram]

u cannot rely on the bas module to share global variables.

it will work fine so long your objects keep running on the same thread..

if an object happens to be instantiated on a separate thread..it will not have the global variables..ie., this particular object will have the initial values only