RE: how bad is soap?

["Patrick R. Gili" <pgili@cisco.com>]

Juergen,

I don't think its a matter of complexity so much as a matter of
return on the investment.  First, the SOAP header can become quite
large and verbose.  Second, one of the reasons for using XML is
human-readability; that is, it eases the process of development,
debugging and maintenance without requiring special tools and
utilities.  Have you tried to read a SOAP header lately?  Argh.

Patrick Gili

> -----Original Message-----
> From: owner-xmlconf@ops.ietf.org [mailto:owner-xmlconf@ops.ietf.org]On
> Behalf Of Juergen Schoenwaelder
> Sent: Wednesday, April 23, 2003 8:09 AM
> To: xmlconf@ops.ietf.org
> Subject: how bad is soap?
>
>
>
> People often argue that SOAP is somehow a bad complex thing and will
> definitely not work on routers and such. When talking to these folks,
> it often turns out that they have never really looked at SOAP
> implementations or believe that SOAP requires Java, complex tools are
> such things to be used, which certainly is not really the case.
>
> I recommend that people who only have a vague idea how SOAP
> implementations can look like in practice take some time to download
> the gSOAP implementation and to play with it. (No, I am not involved
> in this project.)
>
> 	http://www.cs.fsu.edu/~engelen/soap.html
>
> Having seen other RPC systems before, I believe this implementation
> does really not perform bad. But please make up your own mind.
>
> /js
>
> --
> Juergen Schoenwaelder		International University Bremen
> Phone: +49 421 200 3587		P.O. Box 750 561, 28725 Bremen, Germany
> Fax:   +49 421 200 3103		<http://www.iu-bremen.de/>
>
> --
> 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/>
>



--
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/>