Re: XML versus SOAP/WSDL Performance

[Aiko Pras <pras@ctit.utwente.nl>]

That paper primarily compares (various kinds of) SOAP to Corba, Java/RMI 
etc. What I am interested in, however, is to understand the fundamental 
performance differences between SOAP/WSDL and "plain" XML. In other 
words: I want to understand why there is in this community a strong 
support for XML, but reluctance with respect to SOAP/WSDL.

From your mail I understand that your main concern is in the use of 
HTTP. To understand this better, did you want to say that:
1) the HTTP specifications are such that performance will
   always be a problem?
2) HTTP implementations are just lousy
3) the "mapping of SOAP to HTTP" specifications are such that
   performance will always be a problem?
4) (current) SOAP implementations do a lousy job of mapping
   to HTTP (this is what I believe Scott is saying)


Aiko



Juergen Schoenwaelder wrote:
> > > > > > Aiko Pras writes:
> Aiko> Recently I've had a number of discussions on the performance
> Aiko> differences between network management approaches that use XML
> Aiko> technology, and approaches that use web services (SOAP/WSDL). Is
> Aiko> there anyone who has real experience in this area, or know
> Aiko> pointers to studies on this?
>
> Since you have been at the NMRG meeting, you should have read
>
> http://joe.lindsay.net/webservices/rutgers-p2p-p2pws02-soap.pdf
>
> which gives some insights. In general, I think that using HTTP as the
> underlying transport seems awkward from an architectural point of view
> and causes some additional problems that would not exist if people
> would be using a real transport protocol (or a secure version of it)
> as a transport.
>
> /js


--
to unsubscribe send a message to xmlconf-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/xmlconf/>