I haven't seen a direct comparison of the performance of Axis vs SOAP. Axis's design is certainly better. Axis uses SAX, and SOAP uses DOM, so at a minimum, I'm sure that Axis performs better and is more scalable when working with large messages. Axis is still in beta and the engineering team hasn't really started trying to optimize performance yet. Axis is defintely not the fastest SOAP implementation on the market. GLUE and WASP offer 3-20x better performance than Axis (depending on message complexity). Both GLUE and WASP use highly optimized XML parsers.
When I say "performance", I'm talking about raw XML message processing time. Many other things can affect performance and scalability, such as what application server / servlet engine you deploy the Web service container in, and whether or not the container can take advantage of the performance and scalability features of underlying servlet engine. For example, in terms of simple performance -- i.e., how many messages can you process in a minute -- WASP runs fastest in standalone mode. But in terms of scalability, WASP runs best in WebLogic. Anne > -----Original Message----- > From: WJCarpenter [mailto:[EMAIL PROTECTED]] > Sent: Friday, September 20, 2002 12:56 PM > To: [EMAIL PROTECTED] > Subject: RE: Axis vs. Apache SOAP > > > > [Axis] offers better performance than Apache SOAP. > > Do you know of any work actually comparing the performance of the > two? I see this claim sometimes, but when I ask about it I usually > get no response or "well, it's designed to be faster". I don't doubt > that Apache SOAP is slow; I just wonder if the claims of Axis being > faster are justified or merely untested hopes. > > > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
