Abandon "Remoting" completely

[Mike]

There is not going to be such a thing as "remoting" 2 years from now.
I still see people working with it, and I wonder why they are not
keeping up.

Windows Communication Foundatoin, aka .Net 3.0, completely replaces
that. Why does anyone waste time on something that won't be around
soon?

[Michael Nemtsev]

Hello Mike,

Firstly, remoting is not just call between components in the network but
calls in your single app, for example between appdomains
Secondly, WCF is not released yet, and for the most of production projects
using it isn't appropriate.

MThere is not going to be such a thing as "remoting" 2 years from now.
MI still see people working with it, and I wonder why they are not
Mkeeping up.
M>
MWindows Communication Foundatoin, aka .Net 3.0, completely replaces
Mthat. Why does anyone waste time on something that won't be around
Msoon?
M>
---
WBR,
Michael Nemtsev :: blog: http://spaces.msn.com/laflour

"At times one remains faithful to a cause only because its opponents do not
cease to be insipid." (c) Friedrich Nietzsche

[Arnaud Debaene]

"Mike" <ra****@lygenerated.coma écrit dans le message de news:
ag********************************@4ax.com...

>
There is not going to be such a thing as "remoting" 2 years from now.
I still see people working with it, and I wonder why they are not
keeping up.

Windows Communication Foundatoin, aka .Net 3.0, completely replaces
that. Why does anyone waste time on something that won't be around
soon?

??? And what would you use *today* to fill roll that Remoting fit quite well
????

Arnaud
MVP - VC

[Peter Bromberg [C# MVP]]

Mike,
People "waste time" with it because they've built entire app infrastructures
around the fact that it is there since .NET 1.0 BETA.

Now in .NET 2.0 you have the IPC channel (named pipes) which I have seen
some claim is 80 times faster. Fortunately, I use an interop named pipes
transport that doesn't rely on remoting or MarshalByRefObject.

But, Remoting is not "going away" by a long shot.
Peter

--
Co-founder, Eggheadcafe.com developer portal:
http://www.eggheadcafe.com
UnBlog:
http://petesbloggerama.blogspot.com


"Mike" wrote:

>
There is not going to be such a thing as "remoting" 2 years from now.
I still see people working with it, and I wonder why they are not
keeping up.

Windows Communication Foundatoin, aka .Net 3.0, completely replaces
that. Why does anyone waste time on something that won't be around
soon?

[Marc Gravell]

Windows Communication Foundatoin, aka .Net 3.0

Isn't that like saying "Germany, aka Europe"?

;-p

Marc

[Dan Holmes]

Peter Bromberg [C# MVP] wrote:

Mike,
some claim is 80 times faster. Fortunately, I use an interop named pipes
transport that doesn't rely on remoting or MarshalByRefObject.

What is that? Not inheriting from MarshalByRefObject would be really handy.

dan

[Peter Bromberg [C# MVP]]

Dan,
sample implementation for a "Cache" here:

http://www.eggheadcafe.com/articles/20060404.asp

Peter

--
Co-founder, Eggheadcafe.com developer portal:
http://www.eggheadcafe.com
UnBlog:
http://petesbloggerama.blogspot.com


"Dan Holmes" wrote:

Peter Bromberg [C# MVP] wrote:

Mike,
some claim is 80 times faster. Fortunately, I use an interop named pipes
transport that doesn't rely on remoting or MarshalByRefObject.

What is that? Not inheriting from MarshalByRefObject would be really handy.

dan