Hi,

Reading about WCF I had this feeling that .net remoting has been left
behind. There's a lot about webservices but nothing about remoting
which suprises me as MS was encouraging to use it in non-heterogeneous
applications before .net 3.0 was released.

This is not a technical question, it is rather about the direction MS
heads in this matter. What's their vision?

/Marcin

I believe WCF replaces .Net Remoting.

Robin S.
Ts'i mahnu uterna ot twan ot geifur hingts uto.
-----------------------------------------------
<ochocki (AT) gmail (DOT) com> wrote

That is some confusion out there. Remoting still exists and is a good call
in some cases. In fact, WCF also uses remoting internally for some things.

--
William Stacey [C# MVP]
PCR concurrency library: www.codeplex.com/pcr
PSH Scripts Project www.codeplex.com/psobject


"RobinS" <RobinS (AT) NoSpam (DOT) yah.none> wrote

WCF takes all the distributed application technologies (remoting,
webservices, message queuing) and standardizes the way you develop using
these technologies. You write the program once and then with a small config
change you can change the underlying communications method from
HTTP/SOAP/WebService, to TCP/Binary/Remoting, to using MSMQ. So, all these
different technologies have been sucked into this standard programming
model.

"RobinS" <RobinS (AT) NoSpam (DOT) yah.none> wrote

Hello RobinS,

I don't think that's entirely correct to say. WCF follows the philosophy
of SOA, which is regarded by many as being the best currently available
solution to all communication problems. .NET Remoting, similar to many
remote invocation architectures in the past, supports ideas that go beyond
this (server-side stateful objects, for instance). I don't think that all
the reasons that people once had to like these ideas are invalid today...
as usual, and in contrast to what some technical marketing people will
have you believe, the "correct" answer depends on your problem, and to
give it requires deep understanding of that problem as well as the various
alternative technologies for remote invocation.

Of course there's also the matter of which technology will be (most?)
actively developed by its makers - the answer to that could well be WCF,
even though Microsoft have so far said that Remoting would continue to be
part of the package.


Oliver Sturm
--
http://www.sturmnet.org/blog

Thus wrote Oliver,

Just for the record -- you can have stateful services in WCF. It's certainly
a SOA-minded framework, but nothing in it prevents you from doing plain old
OO-RPC using (I)Serializable. Don't forget NetDataContractSerializer.


Amen :-)

Cheers,
--
Joerg Jooss
news-reply (AT) joergjooss (DOT) de

Hello Joerg,

I admit I haven't looked into that in detail. At a glance it looks like
you're right, but it remains unclear to me whether we're really talking
about *server-side* statefulness here, analogous to .NET Remoting. Must
look into that to be sure, I guess. Thanks for filling the gap in any case.


Oliver Sturm
--
http://www.sturmnet.org/blog

Thus wrote Oliver,

A session-capable binding and [ServiceBehavior(InstanceContextMode=InstanceContex tMode.PerSession)]
(which is the default) in your service implementation is all you need for
a stateful service instance.

Cheers,
--
Joerg Jooss
news-reply (AT) joergjooss (DOT) de