Component Load-Balanced Client Design
A client application doesn't do anything different when creating a component that is load balanced than it does when creating one that isn't. The client application simply creates an object, specifying the load-balancing router as the host. The client doesn't know whether the object that resulted from the call is running on a machine it specified or on one to which the writer delegated the object creation. In general, you probably don't want your clients to have to care whether their components are load balanced or not.
A client should be aware that, if a component is load balanced, the death of a server doesn't necessarily mean that the client is useless until the server comes back up. The application cluster ...
Get COM+ Unleashed 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.
