C # Remoting / WCF Client Server Application With Which Technology Can Be Used?

I really do so advice. I have been thinking about a client server project for a while and am going to use .NET. It was originally easy to use 2.0, but recently got VS2008 and thought I should really learn 3.5 as well.

The application will connect one server and many clients. Both the client and the server will need to talk to each other (i.e. two-way communication). This will work over the Internet.

I was going to just use remote access to do this, but is there anything, or for some reason, should I use a different approach since 3.5?

I understand that I may have problems with firewalls where ports can be blocked on the client when I use remote access.

Indeed, I'm looking for suggestions to best handle communication between client and server that would work over the network using .NET (I wish the client could work in other languages ​​as well, but really, but it doesn't matter I guess). Both client and server must be able to call each other's methods.

Thank,

and Merry Christmas.

John

0


source to share


2 answers


I'm just getting started in WCF and am asking a few questions on this topic here. Some things I've learned in the last week or so:



  • This article is excellent: MS Pub-Sub with WCF
  • WCF is the way to go. This dynamic configuration and unified programming model should make it the preferred choice for traditional web services or for remote access.
  • Through configuration, your WCF service can be exposed with a simple HTTP binding allowing it to consume traditional web services.
+2


source


As far as I know, WCF should replace .NET Remoting, so I would go for that.



0


source







All Articles