Gaurav
May 28th, 2000, 01:40 PM
Hi,
I'm building an ActiveX DLL and so far i've had everything in a Single class. Now i was thinking of putting stuff like the constants into a standard module, as well as some helper functions...
So Q#1 is this a good idea?? I know its neater n all as far as code goes... but how good is it with respect to security and process contexts??
An ActiveX DLL in VB cannot be multi threaded. So if i have 300 clients for the DLL, true the DLL will load in the context of the Client but will calls to teh constants or helper functions from the module be streamlined or will they be queued??? Is the module another process?? or does the data load in the clients context??
Q#2
Or what if I implement another class will this cause similar issues?? Lets say i aggregate a class that does all my Database access for me... how good will performance be here?? will the aggregted class have requests q'd?? or will it work seamlessly???
Thanks a ton...
Cheers
Gaurav
I'm building an ActiveX DLL and so far i've had everything in a Single class. Now i was thinking of putting stuff like the constants into a standard module, as well as some helper functions...
So Q#1 is this a good idea?? I know its neater n all as far as code goes... but how good is it with respect to security and process contexts??
An ActiveX DLL in VB cannot be multi threaded. So if i have 300 clients for the DLL, true the DLL will load in the context of the Client but will calls to teh constants or helper functions from the module be streamlined or will they be queued??? Is the module another process?? or does the data load in the clients context??
Q#2
Or what if I implement another class will this cause similar issues?? Lets say i aggregate a class that does all my Database access for me... how good will performance be here?? will the aggregted class have requests q'd?? or will it work seamlessly???
Thanks a ton...
Cheers
Gaurav