-- Lazy (on demand) parsing is definitely an area for improvement. In intermediary services much of the data in the message is not used.
-- Particularly in Axis, direct serialization of XML into registered types (using SAX of cause). In some instances that gives as much as 1/3 memory utilization and much less CPU utilization as well. Currently I am prototyping the change, and it seems to be working well for the most part. > -----Original Message----- > From: KUMAR,PANKAJ (HP-Cupertino,ex1) [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, February 13, 2002 11:41 AM > 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 >
