Web service to web service communication...

  • Thread starter Thread starter almurph
  • Start date Start date
A

almurph

Hi,


A very simple question - Just wondering how does 1 method in a web
service communiate (send or receive info) with another method in
another, seperate web service? Is SOAP involved at all?

Would appreciate all comments,
Thank you,
Al.
 
Hi,


A very simple question - Just wondering how does 1 method in a web
service communiate (send or receive info) with another method in
another, seperate web service? Is SOAP involved at all?

Would appreciate all comments,
Thank you,
Al.

Just because the client participates in a web service does not change
the way the connections work. The approach is that you are still
working with a web service from the client's perspective. From the
services perspective, nothing changes either.

If the two services were both part of the same web application, you
could change this approach by going directly to the classes.
 
Hi,

If they are really used as web services by definition it will use exactly
the same method than for any other client. Of course if both services are on
the same machine you may want to call directly into the class that provides
the implementation (likely why WCF favor a good design by splitting the
service ilmplementation and how it is exposed but you could do this as well
with "old school" ASMX services).

It's best to always tell your exact problem rather than asking a related
question...
 
Hi,


A very simple question - Just wondering how does 1 method in a web
service communiate (send or receive info) with another method in
another, seperate web service? Is SOAP involved at all?

Would appreciate all comments,
Thank you,

It makes no difference as to who the client to a Web service is. It can be
a UI client or a Web service as the client of a Web service that is
servicing the client. SOAP and XML are going to be involved.


__________ Information from ESET NOD32 Antivirus, version of virus signature database 4338 (20090815) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com
 
Back
Top