Login | Register   
RSS Feed
Download our iPhone app
Browse DevX
Sign up for e-mail newsletters from DevX

By submitting your information, you agree that devx.com may send you DevX offers via email, phone and text message, as well as email offers about other products and services that DevX believes may be of interest to you. DevX will process your information in accordance with the Quinstreet Privacy Policy.

Tip of the Day
Language: VB6
Expertise: Intermediate
Aug 3, 2002



Building the Right Environment to Support AI, Machine Learning and Deep Learning

Reduce COM+ context overhead: use non configured classes

In another item in this Tip Bank (see link below), we mention that you can co-locate secondary instances within the context of the caller. If you don't need any services at all for your secondary components, then you don't have to configure them as COM+ components either. You lose the deployment and administrative support that you get from COM+, but you get improved speed and less memory consumption. Prior to COM+ 1.5, this also takes away the configuration trap for "Must be activated in the callers context".

In COM+ 1.5, you can get a similar effect, but without giving up the deployment and administrative support by saying "Must be activated in the default context".

Jimmy Nilsson
Comment and Contribute






(Maximum characters: 1200). You have 1200 characters left.



Thanks for your registration, follow us on our social networks to keep up-to-date