|
-
Mar 10th, 2005, 04:41 PM
#1
Thread Starter
PowerPoster
.NET Remoting
Anyone have experience porting a DCOM architecture to a .NET Remoting architecture? I am looking for the appropriate alternative to DCOM in .NET land, and it looks like .NET Remoting is the way to go.
Comments?
Nobody knows what software they want until after you've delivered what they originally asked for.
Don't solve problems which don't exist.
"If I had eight hours to cut down a tree, I'd spend six hours sharpening my axe." --- Abraham Lincoln (1809-1865)
2 idiots don't make a genius.
-
Mar 11th, 2005, 01:17 AM
#2
Re: .NET Remoting
Try XML Web Services. I am not well versed with it, but it does have its advantages. .NET Remoting would be faster over a network, but XML Web Services are platform independent. Also, XML can be passed across on TCP.
-
Mar 11th, 2005, 09:23 AM
#3
Thread Starter
PowerPoster
Re: .NET Remoting
I failed to mention that I have thoroughly investigated Web Services and the paradigm is inadequate to replace DCOM as a messaging architecture.
Ie.. a web services solution cannot "push" information down to the client (like raising an Event). Rather, the client asks for information, and he gets it. Somewhat like a sneeze.
I think .NET Remoting is the way I have to go. I am getting some books on the topic in the coming week.
Nobody knows what software they want until after you've delivered what they originally asked for.
Don't solve problems which don't exist.
"If I had eight hours to cut down a tree, I'd spend six hours sharpening my axe." --- Abraham Lincoln (1809-1865)
2 idiots don't make a genius.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|