The released version of Visual Basic 6.0 as well as Visual Basic 5.0 with Service Pack 3.0, do not require that the unattended execution option be checked for COM-based objects. You do not have check this option from the Project Properties page for the components shown in Example 5-1 and Example 5-2.
Visual J++ (or COM wrapped Java components) and C++ components both support the both-threaded model, but Visual Basic only supports the single threaded apartment model (STA) at this time. Because of this, object recycling won't occur. However, just-in-time activation is supported with apartment threaded components, including support for the ObjectControl events Activate and Deactivate as shown in Example 5-1.
Mention is made of object pooling. Object pooling is based on the concept of recycling -- that once a client is finished with an object, that object is returned to a pool of like objects, to be used when the same client, or a different client, needs another instance of the object. Based on this, a requirement of object pooling is that the object being pooled must be both-threaded, to make it accessible by different threads.
Also in reference to object pooling: object pooling is not currently implemented, at least it is not implemented with MTS version 2.0 or earlier. If this changes with newer releases, I will amend this information accordingly. As stated earlier, just-in-time activation and connection pooling are implemented, and can be effectively used by any ASP component, regardless of the language used to build the component.
Microsoft has changed its Web site, and many of the links listed in the chapter have changed.
The URLs in the Further Reading section have changed. Instead of:
They should now read: