remoting vs WCF

  • Thread starter Thread starter Amol
  • Start date Start date
A

Amol

HI,
Currently we have a client server application workking on teh Socket
programming. We need to change the application either to remoting or
WCF. I need to justify why we will go for remoting or for WCF. I
tried to search on net advantages and disdvantages of both the
technologies.
The application scenario :

1.The client and the server are both controlled by us.
2. The client passes many different requests to the server with
different arguments.
3. Server processes all the requests.
3.If the server fails in any task it has to intimate the client about
a task fail.
4.Client has to many tasks to send to server with different
parameters.
5. Some more code for different tasks will be added on the server.
6.We need a proper logging in place.
7.We deal with lots of configuration files on the server part.

How much code change is needed to switch from Socket Programming to
Remoting .
Will rewriting the code in WCF be the same effor as changing the code?
Please help me on this issue.
Thanks
Amol
 
Amol said:
HI,
Currently we have a client server application workking on teh Socket
programming. We need to change the application either to remoting or
WCF. I need to justify why we will go for remoting or for WCF. I
tried to search on net advantages and disdvantages of both the
technologies.
The application scenario :

1.The client and the server are both controlled by us.
2. The client passes many different requests to the server with
different arguments.
Click to expand...

WCF service
3. Server processes all the requests.
Click to expand...

WCF service
3.If the server fails in any task it has to intimate the client about
a task fail.
Click to expand...

WCF service can throw excptions across bounderies.
4.Client has to many tasks to send to server with different
parameters.
Click to expand...

You send an object that has poperties for the parms to be passed to the WCF
service, to eliminate many parms being passed on an interface.
5. Some more code for different tasks will be added on the server.
Click to expand...

You add a interface to the WCF service and an Operational Contract that
executes a method in the BLL or DAL, since they can sit behind a WCF
service, and you can add as many methods as you want pointed to by the WCF
service interface and Operational Contracts.
6.We need a proper logging in place.
7.We deal with lots of configuration files on the server part.

How much code change is needed to switch from Socket Programming to
Remoting .
Click to expand...

WCF has all the commnications factors covered by using WCF Web, TCP/IP
remoting, Named Pipe, and MS Message Queue WCF service types.
Will rewriting the code in WCF be the same effor as changing the code?
Please help me on this issue.
Click to expand...

MS is leveraging out of .NET legacy communications such as Remoting, legacy
Web service, etc, etc, which have all been incorporated in the WCF service
types, to make things easier to be use by the developer.

And new .NET technology will be geared towards using WCF. And WCF is kind of
simple to use, when you get a good book that show you the basics. And if you
have database access, then you would use ADO.NET Entity Framework, since
it's an implicit serialized datacontract to WCF.

You may also want to look at Model View Controller or Model View Presenter
design patterns.





__________ Information from ESET NOD32 Antivirus, version of virus signature database 4474 (20091001) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com
 
You would bether go for WCF as remoting is a dead end as MS favored the
newer WCF technologies
isn`t that justification enough to choose WCF ?

everything you mentioned can be done with WCF technologies

HTH

Michel
 
Back
Top