I don't think that the transport protocol will significantly affect overall performance. The bottleneck is invariably in XML processing. That's where we need to concentrate. In WASP we use a pull parser, which is faster than DOM or SAX. But I'm sure we can think up even faster ways to process the message.
Anne > -----Original Message----- > From: Sadiq, Waqar [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, February 13, 2002 3:08 PM > To: [EMAIL PROTECTED] > Subject: RE: SOAP Performance - What's next > > > Has anyone looked at DIME at > http://gotdotnet.com/team/xml_wsspecs/dime/default.aspx. To me, it seems > like the lack of a binary encoding format is the only thing that > is going to > make a performance difference. > > > _______________________________________________ > Waqar Sadiq > > EDS EIT EASI - Enterprise Consultant > MS: H3-4C-22 > 5400 Legacy Drive > Plano, Texas 75024 > > phone: +01-972-797-8408 (8-837) > e-mail: [EMAIL PROTECTED] > fax: +01-972-605-4071 > _______________________________________________ > > > > -----Original Message----- > From: KUMAR,PANKAJ (HP-Cupertino,ex1) [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, February 13, 2002 1:41 PM > To: '[EMAIL PROTECTED]' > Subject: RE: SOAP Performance - What's next > > > Dan Davis Wrote: > > I'm likely doing my masters thesis on SOAP/WSDL and I'm looking for > > fallow ground, or at least a place to make a difference. > > > > What other improvements to SOAP performance other than SAX vs. DOM > > are out there? What's next after Axis to improve SOAP's performance? > > > > What do Axis developers expect for SOAP performance under Axis? > > > > What other areas do you all suggest? > > -- May be an efficient encoding of SOAP documents ( described in WSDL and > agreed upon by both ends ) to reduce size and improve parsing efficiency. > -- May be a mixed-mode ( part DOM, part SAX ) processing of SOAP > documents ( > as pure SAX processing has turned out to be so difficult ). > > /Pankaj >
