C# Remoting ???

  • Thread starter Thread starter sandy82
  • Start date Start date
S

sandy82

I coded a simple example in c#
In which their is a client and a server using a dll . I am confused on
the Point that u have to use the .dll on both sides .Cant we have a
solution of having a dll on server side and the client calling the
remote service .
Also Can any1 tell that whats the Practical use of remoting .How u
differentiate btw remoting and Web Services
 
..NET supports both binary remoting and web services. There are a lot
of things to consider when choosing the right solution for you
application, but generally web services are better if you need to
expose you service across a firewall using HTTP, and binary remoting is
better if your service will be contained with your local network and
performance is a priority.

HTH,

Chris
 
...
I coded a simple example in c# In which their is a client and
a server using a dll . I am confused on the Point that u have
to use the .dll on both sides .Cant we have a solution of
having a dll on server side and the client calling the
remote service .
Click to expand...

That depends on your definition of "remoting".

You can absolutely access remote servers without the need for any dll, e.g.
by using raw sockets and reading/writing "raw bytes" to the streams, but
then you'll also need to write all of the code needed to "translate" what
you read and write through the streams.

If you mean using the Remoting libraries in .NET, you'll come to this
situation:

How to know what methods you can call
from the client on the server?

That's where the dll:s come into play. In them are the classes and
interfaces needed for the client to know what to commuicate with.
Also Can any1 tell that whats the Practical use of remoting.
How u differentiate btw remoting and Web Services
Click to expand...

In general, when using web services, you're locked into using a text-based
transfer protocol (using XML), while Remoting (as above) in simple terms,
doesn't need that conversion/deconversion to/from text, but sends "the
objects" as they are, hence a more efficient communication.

// Bjorn A
 
When u call a remote method stored on some other machine or may b on
same machine .. a similar of Remote Procedure Call .
I think Binary Remoting is the same but I still Doubt can u explain a
bit more .
 
When u call a remote method stored on some other machine or may b on
same machine .. a similar of Remote Procedure Call .
I think Binary Remoting is the same but I still Doubt can u explain a
bit more .
 
Hi Chris. This is more for the Doc writers...
I never understood why they make it a point of saying that in the docs.
Remoting is really just an abstraction over sockets ( or NegotiatedStream in
secure remoting). So at the low level, it just uses TCP sockets like any
other TCP app on the net. Firewalls don't have an issue with sockets. Its
really a lazy way to say "I don't want to have to talk about firewall
configurations, so I will just say use Web services (HTTP) over port 80 as
it is probably configured already and we want to push IIS." But you can
still use remoting over HTTP, so not sure what they are talking about.
Remoting works fine over the INET. The issue, imo, is more that with
remoting you have to deploy a server side, were with IIS you deploy dlls and
IIS hosts them. The other issue is how you want to program with objects or
XML and web services. They both have pros and cons I guess.

--
William Stacey [MVP]

| .NET supports both binary remoting and web services. There are a lot
| of things to consider when choosing the right solution for you
| application, but generally web services are better if you need to
| expose you service across a firewall using HTTP, and binary remoting is
| better if your service will be contained with your local network and
| performance is a priority.
|
| HTH,
|
| Chris
|
 
Vadym Stetsyak said:
Hello, sandy82!

s> I coded a simple example in c#
s> In which their is a client and a server using a dll . I am confused on
s> the Point that u have to use the .dll on both sides .

dll has to be on both sides as it holds metainfo about types.
As you use typed var in the client and server.
Click to expand...

If memory serves.
If you design the server side as implementing an interface. Then all the client needs is the
interface and not the class itself.

Bill
 
Back
Top