Daniel is talking about the Apache SOAP implementation, not the SOAP protocol, so I'll answer in terms of the protocol.
There are a number of ambiguities and inaccuracies in the SOAP 1.1 specification -- most of which have been resolved in the new SOAP 1.2 specification [1]. This biggest issue that I have with SOAP )both 1.1 and 1.2) is that it has too many options. I'd prefer to do away with SOAP encoding and the RPC convention entirely (only support document/literal). I'd also like to see some guidelines for how to map language structures to XML structures -- but I'd say that this is an area for the language-specific standards groups, not the SOAP protocol. I'd also like to see some formal standards for dealing with attachments -- which may be formalized by the SOAP 1.2 attachment feature. I'd say that the only serious, unavoidable disadvantage to the SOAP protocol is the issue of performance-intensive XML processing. It is an inherent attribute of the SOAP protocol. It takes lots of cycles and imposes lots of latency, but the advantages of using XML encoding far outweigh the disadvantages of XML processing overhead. [1] http://www.w3.org/TR/soap12-part1/ Best regards, Anne ----- Original Message ----- From: "Daniel Zhang" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, June 06, 2003 2:15 PM Subject: Re: SOAP improvements. > SOAP weakness contains but not limited to: > - Not support WSDL > - Use DOM instead of SAX(AXIS improved on this) > - Poor support for layered architectures > > aliya khan wrote: > > > > > > > Hi > > what improvement can be made to the soap protocol? > > & what is the greatest weakness of this protocol? > > > > _________________________________________________________________ > > STOP MORE SPAM with the new MSN 8 and get 2 months FREE* > > http://join.msn.com/?page=features/junkmail > > >
