P
paul.drummond
Hi all,
I am new to whole idea of "web services" and architectures such as .NET
and J2EE so please bare with me. I am trying to research as much as
possible before asking silly questions but there is so much out there!
I need to start somewhere!!!
My question is, when developing local non-web based applications, is
SOAP still the standard way to communicate between applications in the
..NET world?
I realise SOAP is less efficient than other mechanisms and I also
realise the decision to use SOAP depends on the problem domain (whether
the app could potentially become web-based is certainly a factor) but
that's not the qeustion - regardless of the advantages/disadvantages
(which I will evalulate at a later time) I am just wondering whether
SOAP is used this way in real world scenarios, as a local process
communication mechanism or whether it's just too slow (for example) for
this to be viable.
I am new to whole idea of "web services" and architectures such as .NET
and J2EE so please bare with me. I am trying to research as much as
possible before asking silly questions but there is so much out there!
I need to start somewhere!!!
My question is, when developing local non-web based applications, is
SOAP still the standard way to communicate between applications in the
..NET world?
I realise SOAP is less efficient than other mechanisms and I also
realise the decision to use SOAP depends on the problem domain (whether
the app could potentially become web-based is certainly a factor) but
that's not the qeustion - regardless of the advantages/disadvantages
(which I will evalulate at a later time) I am just wondering whether
SOAP is used this way in real world scenarios, as a local process
communication mechanism or whether it's just too slow (for example) for
this to be viable.