When to use sockets and when to use remoting
-
I am at the moment building a client/server application using .NET. This is a Win Forms based app and for the communication I thought I would use sockets. But someone just mentioned "why dont you use remoting?". I dont know how skilled this person is and how much experience he has with remoting and/or sockets so I cant really know based on what he made that comment. The application is nothing out of the ordinary really. The server has a database and the client interacts with the server and inserts, updates, deletes and requests data to/from the server. All clients and the server are all on a local network. What I really need to know is, how do I know when I have an application that is a good candidate to use remoting for its network communication?
-
I am at the moment building a client/server application using .NET. This is a Win Forms based app and for the communication I thought I would use sockets. But someone just mentioned "why dont you use remoting?". I dont know how skilled this person is and how much experience he has with remoting and/or sockets so I cant really know based on what he made that comment. The application is nothing out of the ordinary really. The server has a database and the client interacts with the server and inserts, updates, deletes and requests data to/from the server. All clients and the server are all on a local network. What I really need to know is, how do I know when I have an application that is a good candidate to use remoting for its network communication?
My take on this :- Use remoting if client and server are guaranteed to be .NET If a non-.NET client needs to connect to the server, use sockets Nish