Both sides. (you have to parse the message on both sides) There are other issues that affect performance and (even more so) scalability -- especially on the server -- such as lifecycle management. But these other performance issues are negligible next to parsing.
We had another discussion on this list [1] recently about performance. The JAX-RPC spec forces the use of SAX, which isn't the most efficient way to parse structured messages. [1] http://marc.theaimsgroup.com/?l=axis-user&m=104429792424850&w=2 Anne > -----Original Message----- > From: Luís Fraga [mailto:[EMAIL PROTECTED]] > Sent: Monday, February 10, 2003 10:16 AM > To: [EMAIL PROTECTED] > Subject: Re: Axis performance in compare with XRPC (reference > implementation from SUN)! > > > Hi Anne! > > The issues you are referring to concern mainly server side, client side > or both? > > Thanks for any comments, > Luís > > Anne Thomas Manes wrote: > > >A lot of the performance differences come from the parsing > technology used. > >GLUE uses Electric XML, which is a highly optimized JDOM-like > parser. WASP > >uses a pull parser. > > > > > > > >>-----Original Message----- > >>From: Luís Fraga [mailto:[EMAIL PROTECTED]] > >>Sent: Monday, February 10, 2003 7:20 AM > >>To: [EMAIL PROTECTED] > >>Subject: Re: Axis performance in compare with XRPC (reference > >>implementation from SUN)! > >> > >> > >>10-15x faster than Axis!!??? I will have to check that! > >>What are your toughts regarding these performance issues? > >> > >> Luís > >> > >> > >> > >>Anne Thomas Manes wrote: > >> > >> > >> > >>>You'll find Axis performance much faster than Sun's JAX-RPC RI. It also > >>>provides much easier tools. But the commercial implementations are much > >>>faster and easier still. There are free versions available for > >>> > >>> > >>both GLUE and > >> > >> > >>>WASP. GLUE Standard is always free. The footprint is tiny, too. See > >>>http://www.themindelectric.com. WASP is always free for > >>> > >>> > >>development, and you > >> > >> > >>>can get a free deployment license for a single CPU (multi-CPUs require > >>>payment). See http://www.systinet.com. These two implementations > >>> > >>> > >>offer the > >> > >> > >>>best performance (10-15x faster than Axis) and the best tools. > >>> > >>>Anne > >>> > >>> > >>> > >>> > >>> > >>>>-----Original Message----- > >>>>From: Armond Avanes [mailto:[EMAIL PROTECTED]] > >>>>Sent: Saturday, February 08, 2003 2:45 AM > >>>>To: [EMAIL PROTECTED] > >>>>Subject: Axis performance in compare with XRPC (reference > implementation > >>>> > >>>> > >>>>from SUN)! > >>> > >>> > >>>>Hi SOAP Folks, > >>>> > >>>>Anyone has compared the performance of these two implementations > >>>>(Apache's Axis and Sun's XRPC) in a real environment?! > >>>> > >>>>FYI, I'm in the phase of replacing the communication layer (which is > >>>>reference implementation of SUN) of the application, I'm working on, > >>>>with Axis. Sun's implementation generates so many classes and > uses many > >>>>libraries so causes the whole result (application jars, ear's, war's, > >>>>etc) to be very huge. Another side effect is the build time of the > >>>>project, which is really much! > >>>> > >>>>I need all your ideas/suggestions/comments in this regard. > >>>>What problems may I get into with Axis? How's the performance > in compare > >>>>with other implementations? Is there any better alternative than Axis > >>>>(free for sure!) And so on... > >>>> > >>>>Best Regards, > >>>>Armond > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>> > >>> > >>> > >>> > >>> > >> > >> > >> > > > > > > > > > > > > >
