Re: WCF vs Remoting
- From: Spam Catcher <spamhoneypot@xxxxxxxxxx>
- Date: Tue, 25 Sep 2007 15:28:34 GMT
"Scott M." <s-mar@xxxxxxxxxxxxx> wrote in
news:uE$inWs$HHA.4584@xxxxxxxxxxxxxxxxxxxx:
My understanding is that WCF isn't a replacement for Remoting, it's an
additional layer on top of remoting (or web services).
Although Microsoft says that WCF is a complement for Remoting - in reality,
WCF is remoting's replacement.
For all intents and purposes - remoting is dead with .NET 3.0.
If you're going to start a project, WCF is a very attractive alternative to
remoting and supports many of the features that were lacking (i.e.
bidirectional messages, authentication and authorization).
However remoting does still have some advantages - the ability to use
shared interfaces. WCF uses proxies methods instead ... and have similar
limitations to a web service (i.e. no method overloading, no sharable
interfaces, etc.). But overall, WCF is such a major enhancement that it the
disadvantages are minor in comparison to the new features.
.
- References:
- Re: WCF vs Remoting
- From: Scott M.
- Re: WCF vs Remoting
- Prev by Date: RE: Problems with Filesystemwatcher and Web Service
- Next by Date: Re: WCF vs Remoting
- Previous by thread: Re: WCF vs Remoting
- Next by thread: Re: WCF vs Remoting
- Index(es):
Relevant Pages
|