.NET Remoting 101

  • Thread starter Thread starter Sathyaish
  • Start date Start date
S

Sathyaish

I have a basic question about remoting in .NET v1.1

Please briefly rummage through the following articles in the given
sequence:


http://msdn.microsoft.com/en-us/library/xws7132e(VS.71).aspx

http://msdn.microsoft.com/en-us/library/txct33xt(VS.71).aspx

http://msdn.microsoft.com/en-us/library/8019cc4e(VS.71).aspx

http://msdn.microsoft.com/en-us/library/y6dc64f2(VS.71).aspx


In the last article titled 'Building a Client Application', the author
copies the same RemotableType.dll into the folder that has the
Client.exe application. This confused me.

In a .net remoting scenario, does the client application need to have
the binary image of the actual remotable type? If it does, what is the
need for remoting then? Doesn't it defeat the purpose of remoting in
the first place? What if the RemotableType.dll was a third party
service that I just needed to use? Would I still need the binary image
of the dll? I was thinking the client just needs the public interface
of the remotable type in order to create a proxy, and not the entire
implementation of the remotable type in its binary.
 
In a .net remoting scenario, does the client application need to have
the binary image of the actual remotable type?
Click to expand...

Not really. You could have the remoting object exposed as an interface, in
which case you would need to share the interface dll only.

If it does, what is the
need for remoting then?
Click to expand...

Execution takes place on the server.
 
Not really.  You could have the remoting object exposed as an interface, in
which case you would need to share the interface dll only.


Execution takes place on the server.
Click to expand...



Thanks. :-)
 
 
Back
Top