WCF better than Net Remoting??

[AAAAA]

Is WCF better than Net remoting??
What are the adventages of WCF??

Thank you

Cesar

 

[Arne Vajhøj]

Is WCF better than Net remoting??
What are the adventages of WCF??

It is much better of separating the service from
the transport specifics.

Arne

 

[Alex Meleta]

Hi

What's mean better? Advantage is an architecture flexibility (declarative
infrastructure to differ endpoints, transports as so on, some simplification
of security, hosting etc.).

Regards, Alex Meleta
mailto:[email protected]; blog:devkids.blogspot.com

 

[sloan]

WCF is more abstract and "higher" level then .Net Remoting.
Thus you can write the same code and expose endpoints which support .Net
Remoting (and WebServices and MSMQ).

I find it easier to use as well, once you get through the basics.


Here is a sample I made:
http://sholliday.spaces.live.com/Blog/cns!A68482B9628A842A!158.entry

Note, I am primary concerned with a "DotNet to DotNet" world (like .Net
Remoting is), and I use interfaces rather than the (most common) proxy
classes on the client. ((<< Loose interpretation of what is happening).

Take a look, and download the example and you'll have a WCF (remot'ish type)
example up and running in about 5 minutes.

Good luck.

 

[not_a_commie]

WCF is also significantly faster than .NET Remoting. Look around on
the web for some benchmarks.

 

[Arne Vajhøj]

WCF is also significantly faster than .NET Remoting. Look around on
the web for some benchmarks.

Significantly yes, but not orders of magnitudes.

http://msdn.microsoft.com/en-us/library/bb310550.aspx

figure 12

Arne

 

[Scott M.]

WCF is really a framework for exposing .NET funcationality to other systems.
Using WCF, you have a standard way of utilizing different transport
protocols for delivering the data payload.

Prior to WCF, if you wanted to develop a *service* that could be used
heterogeniously, you'd create a Web Service, which had its own way of
setting it up, writing the code and consuming the service. If you wanted a
homogenious architecture, you might use .NET Remoting, which used different
transport protocols than Web Services and required a different way of coding
the client and server pieces.

With WCF, you can utilize whatever transport protocols suit your needs (TCP,
SOAP, MQ), but still build the WCF service the same way, just with some
modifications to the "plumbing".

So, it's not that WCF is "better" than remoting, since the two are directly
comparable. WCF allows you to expose remoting functionality, but in a
standardized way.

-Scott