Define SingleCall activation mode in .Net Remoting. - The SingleCall remote server types always has only one instance per client request.
- Generally the next method invocation is serviced by a different instance.
- The functionality provided by the SingleCall type is straightforward in terms of design.
- The no state management is provided by using this mechanism and is bad if you want some but ideal if you don't.
- This mode is an ideal choice as you get exactly one instance per request only if care about load balancing and scalability is taken rather than the state.
- Own state management can be provided for SingleCall objects if the developer wants, but this state data would not reside within the objects themselves as a new object identity is instantiated with each new method call.