Microsoft® .NET Distributed Applications: Integrating XML Web Services and .NET Remoting
by Matthew MacDonald
SingleCall Objects
The preceding example uses a client-activated type because its behavior closely resembles that of an ordinary, in-process object. Remoting also provides two types of server-activated (or "well-known") objects, which the client must connect to using the specified URL. The first type is SingleCall.
SingleCall objects are the most efficient and common type of remotable object in an enterprise application because they are extremely lightweight and efficient. With a SingleCall object, the object is created at the beginning of every method invocation and released at the end. This ensures that valuable server memory is never retained for long. The client retains a reference to the proxy for the object as long as it wants, and the proxy ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access