> That's probably not a good solution. It sounds to me SOAP is > good for short messages. Not true at all. There are no size limitations in the design of SOAP format. Some of today's toolkits do not handle large messages well, but they also don't handle SOAP itself well sometimes. :) What he saw, was performance hit of using DOM XML model. Attachments have specifically been designed for large data blocks, that for some reason may not be favorable to stick in the body/header. (Large XML data, Binary data, etc) Use SAX and possibly attachments... :)
> -----Original Message----- > From: Zhang, Li [mailto:[EMAIL PROTECTED]] > Sent: Monday, February 04, 2002 3:09 PM > To: '[EMAIL PROTECTED]' > Subject: RE: High Volume > > > That's probably not a good solution. It sounds to me SOAP is > good for short > messages. > > Li > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]] > Sent: Monday, February 04, 2002 2:19 PM > To: [EMAIL PROTECTED] > Subject: High Volume > > > Does anyone here have experience with high volumes using > either Axis or > Apache SOAP? > > We would like to use Axis to provide an API into our data, > however we need > to return 150,000 rows minimum with each row consisting of > over 2k of data > (not counting xml overhead). > > A quick test returning an array of 1000 objects consisting of > 5 Strings & 4 > Integers takes 65 seconds. When I run the counts up to 10,000 > I get out of > memory errors on the client. > > Any guidance would be appreciated. > > Mickey Coulter > >
