Re: C# Remoting ???
- From: "Bjorn Abelli" <bjorn_abelli@xxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 11 Apr 2006 13:13:28 +0200
"sandy82" wrote...
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 .
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
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
.
- References:
- C# Remoting ???
- From: sandy82
- C# Remoting ???
- Prev by Date: Re: C# Remoting ???
- Next by Date: Re: Difference between returning null and array with zero elements
- Previous by thread: Re: C# Remoting ???
- Next by thread: Re: C# Remoting ???
- Index(es):
Relevant Pages
|
