Object Pooling
A traditional client/server application maps clients directly to server resources in a one-to-one relationship. If there are 10 clients in a system, 10 data objects will be in use. If 1000 clients are attempting to commit data, there will be 1000 data objects and potentially 1000 simultaneous database connections—a much less scalable situation.
To counter this problem, COM+ introduces different types of instance management: object pooling and JIT activation. Object pooling is the most significant of the two. It allows a small set of objects to be reused for a large number of clients. Object pooling is conceptually similar to connection pooling: A "pool" of available, instantiated objects is retained permanently. When a client creates ...
Get Microsoft® .NET Distributed Applications: Integrating XML Web Services and .NET Remoting now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
