This approach lets you create either server-side or client-side objects, depending on your needs. What are those needs? Are you already using Remoting in your applications? Did this article help? Let us know in the csharp.general discussion group.
.NET Remoting provides a powerful way to use remote objects as if they existed locally, using interfaces and the factory pattern.
by David Talbot
October 21, 2002
The .NET framework has a number of powerful Remoting features to make working with remote objects simple especially in the client side code. You can use factory patterns to enable powerful features in the client side code. However, the client side code uses nothing more than ordinary interfaces.
Why not a Web Service?
Remoting provides a number of advantages over Web services but we can start with the way you use them. Web services are the equivalent of static function libraries. If the client creates an instance of the Web service and modifies a member variable of the object with one method call, then attempts to read the value from another method call, the value will be the default value for that variable, not the new value. That's because Web services don't maintain session state without considerable hacking outside of the SOAP standard. Therefore, when you need the ability to use remote objects, rather than remote methods, Remoting is the way to go.
It's quick, easy and you get access to all the articles on DevX.
This registration/login is to allow you to read articles on devx.com. Already a member?
To become a member of DevX.com create your Member Profile by completing the form below. Membership is free!
