I dont think I agree. I feel there is nothing inherently in the SOAP spec that defies usage in high volume conditions, more towards the matter that most current implementations are DOM based and so... I think it would be a nice excercise to design these high volume as well as "continous stream" use cases into Axis. Any takers? I could help.
Mukund Balasubramanian Zhang, Li wrote: >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 >
