To: Tony Viola who wrote (130044 ) 3/17/2001 10:09:31 AM From: Amy J Respond to of 186894 Hi Tony, regarding .NET, I like how Microsoft's XML messaging requires more CPU power. Of course, Sun is complaining about it from an efficiency standpoint. But for us this means, more chips for the gorilla: "However, XML messaging fans argue that those disadvantages are negligible, given the rapidly increasing speed of parsers and CPUs." Here's some clips from an article: internetworld.com Internet World March 15, 2001 .NET Analysis XML as a Distributed Computing Protocol By David F. Carr [...] XML messages suck up more bandwidth and have to be run through a parser before processing. However, XML messaging fans argue that those disadvantages are negligible, given the rapidly increasing speed of parsers and CPUs. Besides, they point to the success of the Web, which is also based on relatively verbose protocols but achieved far more widespread adoption than any competing network computing technology. And because XML messages are inherently open-source[...]A protocol that is simple and open also stands the best chance of being implemented on a wide variety of operating systems and programming languages. ... But Anne Manes, director of market innovation at Sun Microsystems Inc., says [...] “XML messaging is certainly not going to be anywhere near as efficient as binary invocation, and when I'm trying to deal with millions of calls per second I don't want to deal with all the extra translation, if possible.” According to her numbers, using SOAP will be 5- to 30-times slower, depending on the amount of data and the complexity of the operation. When it comes to distributing services outside the firewall, Sun acknowledges that XML messaging is destined to be more universally accepted than any Java-centric technology, she says [...].