You are viewing a plain text version of this content. The canonical link for it is here.
Posted to soap-user@ws.apache.org by Gus Delgado <gu...@netquotient.com> on 2001/02/14 16:39:22 UTC
SOAP abstract
I had to write an article about soap to share with other developers in my
company, I would like to get some feedback from the SOAP community on it, so
if you have the time to read it and give me some pointers, I would really
really appreciated.
here is the url http://dgus.addr.com/soap/soap_abstract.html
thanks in advance.
Gus
RE: SOAP abstract
Posted by Gus Delgado <gu...@netquotient.com>.
Alex,
Thanks for the input
-----Original Message-----
From: Aleksandar Milanovic [mailto:amilanovic@galdosinc.com]
Sent: Wednesday, February 14, 2001 1:32 PM
To: soap-user@xml.apache.org
Subject: Re: SOAP abstract
Hi Gus,
It's not that I don't like RPC but I don't see a reason to limit SOAP to
only one of its applications which happens to be RPC. Therefore, the very
first sentence of your article (given below) is not untrue, but doesn't
reveal the full power of SOAP.
"SOAP is an XML (Extensible Markup Language) based protocol that provides
business-to-business communication by wrapping RPC calls (Remote Procedure
Calls) in XML files, and sending these files using standard Internet HTTP. "
This sentence would be more meaningful if RPC were everything you're
interested in. However, your article is about SOAP and not SOAP-RPC only.
I haven't read the rest :).
thx
Alex
----- Original Message -----
From: "Gus Delgado" <gu...@netquotient.com>
To: <so...@xml.apache.org>
Sent: February 14, 2001 7:39 AM
Subject: SOAP abstract
> I had to write an article about soap to share with other developers in my
> company, I would like to get some feedback from the SOAP community on it,
so
> if you have the time to read it and give me some pointers, I would really
> really appreciated.
>
> here is the url http://dgus.addr.com/soap/soap_abstract.html
>
> thanks in advance.
>
> Gus
>
RE: SOAP abstract
Posted by Gus Delgado <gu...@netquotient.com>.
Alex,
Thanks for the input
-----Original Message-----
From: Aleksandar Milanovic [mailto:amilanovic@galdosinc.com]
Sent: Wednesday, February 14, 2001 1:32 PM
To: soap-user@xml.apache.org
Subject: Re: SOAP abstract
Hi Gus,
It's not that I don't like RPC but I don't see a reason to limit SOAP to
only one of its applications which happens to be RPC. Therefore, the very
first sentence of your article (given below) is not untrue, but doesn't
reveal the full power of SOAP.
"SOAP is an XML (Extensible Markup Language) based protocol that provides
business-to-business communication by wrapping RPC calls (Remote Procedure
Calls) in XML files, and sending these files using standard Internet HTTP. "
This sentence would be more meaningful if RPC were everything you're
interested in. However, your article is about SOAP and not SOAP-RPC only.
I haven't read the rest :).
thx
Alex
----- Original Message -----
From: "Gus Delgado" <gu...@netquotient.com>
To: <so...@xml.apache.org>
Sent: February 14, 2001 7:39 AM
Subject: SOAP abstract
> I had to write an article about soap to share with other developers in my
> company, I would like to get some feedback from the SOAP community on it,
so
> if you have the time to read it and give me some pointers, I would really
> really appreciated.
>
> here is the url http://dgus.addr.com/soap/soap_abstract.html
>
> thanks in advance.
>
> Gus
>
Re: SOAP abstract
Posted by Aleksandar Milanovic <am...@galdosinc.com>.
Hi Gus,
It's not that I don't like RPC but I don't see a reason to limit SOAP to
only one of its applications which happens to be RPC. Therefore, the very
first sentence of your article (given below) is not untrue, but doesn't
reveal the full power of SOAP.
"SOAP is an XML (Extensible Markup Language) based protocol that provides
business-to-business communication by wrapping RPC calls (Remote Procedure
Calls) in XML files, and sending these files using standard Internet HTTP. "
This sentence would be more meaningful if RPC were everything you're
interested in. However, your article is about SOAP and not SOAP-RPC only.
I haven't read the rest :).
thx
Alex
----- Original Message -----
From: "Gus Delgado" <gu...@netquotient.com>
To: <so...@xml.apache.org>
Sent: February 14, 2001 7:39 AM
Subject: SOAP abstract
> I had to write an article about soap to share with other developers in my
> company, I would like to get some feedback from the SOAP community on it,
so
> if you have the time to read it and give me some pointers, I would really
> really appreciated.
>
> here is the url http://dgus.addr.com/soap/soap_abstract.html
>
> thanks in advance.
>
> Gus
>
Re: SOAP abstract
Posted by Aleksandar Milanovic <am...@galdosinc.com>.
Hi Gus,
It's not that I don't like RPC but I don't see a reason to limit SOAP to
only one of its applications which happens to be RPC. Therefore, the very
first sentence of your article (given below) is not untrue, but doesn't
reveal the full power of SOAP.
"SOAP is an XML (Extensible Markup Language) based protocol that provides
business-to-business communication by wrapping RPC calls (Remote Procedure
Calls) in XML files, and sending these files using standard Internet HTTP. "
This sentence would be more meaningful if RPC were everything you're
interested in. However, your article is about SOAP and not SOAP-RPC only.
I haven't read the rest :).
thx
Alex
----- Original Message -----
From: "Gus Delgado" <gu...@netquotient.com>
To: <so...@xml.apache.org>
Sent: February 14, 2001 7:39 AM
Subject: SOAP abstract
> I had to write an article about soap to share with other developers in my
> company, I would like to get some feedback from the SOAP community on it,
so
> if you have the time to read it and give me some pointers, I would really
> really appreciated.
>
> here is the url http://dgus.addr.com/soap/soap_abstract.html
>
> thanks in advance.
>
> Gus
>
Re: Does SOAP work on TCP/IP
Posted by Denis Haskin <dw...@earthlink.net>.
Abhishek Srivastava wrote:
> Is it necessary for SOAP to make calls over HTTP? I believe that there is a
> servlet that ships with the SOAP SDK and all calls are routed via this
> servlet. ( So the requests and responses are exchanged only over HTTP).
>
> Can I write another server that listens on port 80 but uses a different
> protocol like TCP/IP.
Sure. To quote from the introduction to the SOAP W3C Note: "SOAP provides a
simple and lightweight mechanism for exchanging structured and typed
information between peers in a decentralized, distributed environment using
XML." (http://www.w3.org/TR/2000/NOTE-SOAP-20000508/#_Toc478383486).
This is one of the major complaints I have about the various SOAP
implementations out there now (e.g. Apache SOAP, the various Perl SOAP
modules). There tends to be a lot of focus on using SOAP only for RPC, and for
only using HTTP as the transport. In particular, it seems all of the Apache
SOAP server-side examples use the Apache SOAP listener/RPC router mechanism,
which hides all of the server-side implementation details. That's useful, but
I wish there were some server examples that didn't use that framework (I know,
I know, I should write them...).
I found the Apache SOAP xmethods example to be very useful, even though it's
just the client side, because it manually does some of the work that happens
"under the covers" of the Call.invoke method, and I think would be a good
starting point to understand what one might need to do to use SOAP over a
non-HTTP transport.
While RPC is a *great* use for SOAP (and was one of its design goals) and using
HTTP as the transport makes a lot of sense, people tend to lose sight of the
fact that SOAP is useful for generalized information exchange, and there's
certainly no requirement to use HTTP as the transport protocol.
Just my 2 kopeks...
dwh
Re: Does SOAP work on TCP/IP
Posted by Denis Haskin <dw...@earthlink.net>.
Abhishek Srivastava wrote:
> Is it necessary for SOAP to make calls over HTTP? I believe that there is a
> servlet that ships with the SOAP SDK and all calls are routed via this
> servlet. ( So the requests and responses are exchanged only over HTTP).
>
> Can I write another server that listens on port 80 but uses a different
> protocol like TCP/IP.
Sure. To quote from the introduction to the SOAP W3C Note: "SOAP provides a
simple and lightweight mechanism for exchanging structured and typed
information between peers in a decentralized, distributed environment using
XML." (http://www.w3.org/TR/2000/NOTE-SOAP-20000508/#_Toc478383486).
This is one of the major complaints I have about the various SOAP
implementations out there now (e.g. Apache SOAP, the various Perl SOAP
modules). There tends to be a lot of focus on using SOAP only for RPC, and for
only using HTTP as the transport. In particular, it seems all of the Apache
SOAP server-side examples use the Apache SOAP listener/RPC router mechanism,
which hides all of the server-side implementation details. That's useful, but
I wish there were some server examples that didn't use that framework (I know,
I know, I should write them...).
I found the Apache SOAP xmethods example to be very useful, even though it's
just the client side, because it manually does some of the work that happens
"under the covers" of the Call.invoke method, and I think would be a good
starting point to understand what one might need to do to use SOAP over a
non-HTTP transport.
While RPC is a *great* use for SOAP (and was one of its design goals) and using
HTTP as the transport makes a lot of sense, people tend to lose sight of the
fact that SOAP is useful for generalized information exchange, and there's
certainly no requirement to use HTTP as the transport protocol.
Just my 2 kopeks...
dwh
Does SOAP work on TCP/IP
Posted by Abhishek Srivastava <ab...@india.hp.com>.
Hello,
I am an absolute new bie to SOAP. and trying to figure out a few things.
Is it necessary for SOAP to make calls over HTTP? I believe that there is a
servlet that ships with the SOAP SDK and all calls are routed via this
servlet. ( So the requests and responses are exchanged only over HTTP).
Can I write another server that listens on port 80 but uses a different
protocol like TCP/IP.
regards,
Abhishek.
Does SOAP work on TCP/IP
Posted by Abhishek Srivastava <ab...@india.hp.com>.
Hello,
I am an absolute new bie to SOAP. and trying to figure out a few things.
Is it necessary for SOAP to make calls over HTTP? I believe that there is a
servlet that ships with the SOAP SDK and all calls are routed via this
servlet. ( So the requests and responses are exchanged only over HTTP).
Can I write another server that listens on port 80 but uses a different
protocol like TCP/IP.
regards,
Abhishek.