![]() |
![]() | ![]() | ![]() | ![]() | ![]() | ![]() | ![]() |
| Welcome to Windows Vista Forums. Our forum is dedicated to helping you find solutions with any problems, errors or issues you are experiencing with Windows Vista. The Vista forum also covers news and updates and has an extensive Windows Vista tutorial section that covers a wide range of tips and tricks. |
| |||||||
![]() |
| |
| | #1 (permalink) |
| | remoting vs WCF 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 |
My System Specs![]() |
| | #2 (permalink) |
| | Re: remoting vs WCF 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 "Amol" <amol.koshe@newsgroup> schreef in bericht news:9532866e-a028-4cf9-b1f8-4000324e6b1a@newsgroup Quote: > 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 |
My System Specs![]() |
![]() |
| Thread Tools | |
| |
Similar Threads | ||||
| Thread | Forum | |||
| Remoting | PowerShell | |||
| Re: .Net Remoting Server | .NET General | |||
| Powershell 2.0 with remoting : ok what is Remoting ? | PowerShell | |||