Hello Alexandre ,
There is no rule of thumb that can help you decide which technology to opt
for.
Rather there are certain trade-offs and you will decide what suites you
most. Following is my take on this issue:
Use Sockets communication when:
The relation between client and server is most intimate. And performance is
very important attribute of the system for you. Scalibility is not an issue.
Security is not an issue (for listening on ports that are blocked on firewall
etc).
Use .NET Remoting when:
The platform is known to be Microsoft family of OS. You are tempted to use
..Net Remoting API because it provides extensive support for developing
distributed applications. Communication is meant to maintain state
information.
Use XML Web Services when:
Platform independence is a pre-requisite. Speed of execution (remote call)
is not as critical. All the communication is done through XML based messages.
Stateful communication is not required.
best regards.
"Alexandre (www.pointnetsolutions.com)" wrote:
I am looking at building a distributed system,
and i have been looking at many different options,
in some cases i was thinking of a client server relation
where a client would send a string to the system as a command.
i also looked at the GOF Command pattern which i could somewhat use
with
remoting.
my last option was using a webservice and SOAP...
at the moment i am not talking about a system in specific i am just
wondering which one would be good for what since so many options are
available...
what are your thoughts on each of them, on build time, on structure, on
scallability, on ease of updates and manipulation, security and
especially on speed.
Regards,
Alexandre
