At the beginning of the client/server era, remoting was mostly used for accessing a server's resources. Every database or file server is an implementation of some technique that allows code to be executed remotely. Programming these older frameworks was so difficult a task that few products except for these server-side core services implemented remoting.
1. .NET extends this concept to include the ability to define additional contexts within one running application. Object accesses crossing these boundaries will pass the .NET Remoting framework as well.
Nowadays the building of distributed applications has gotten a lot easier so that it's quite feasible to distribute business applications among various machines to improve performance, scalability, and maintainability.
Was this article helpful?