> You must know > the Content-Length before you write the first byte of data. Not true. Content-Length is not a required HTTP header. In fact many clients don't use it. You can still optionaly use Content-Length inside your MIME bocks to speed up parsing, but even that is optional.
> -----Original Message----- > From: KUMAR,PANKAJ (HP-Cupertino,ex1) [mailto:[EMAIL PROTECTED]] > Sent: Monday, February 04, 2002 5:31 PM > To: '[EMAIL PROTECTED]' > Subject: RE: High Volume > > > SAX processing is only one aspect of processing huge SOAP documents. > > Other issue crops up when you do an HTTP POST of the message. > You must know > the Content-Length before you write the first byte of data. > This requires > creating the text of XML document ( or Mime message, if using SOAP w/ > Attachments ) before streaming it out over the wire. > > Is there a better solution to the problem? I have seen some details of > chunked transfer coding in HTTP 1.1 spec. Does anyone have > any experience in > using this to tackle Content-Length problem ? I mean, is it > possible to send > a SOAP or SOAP w/ Attachment message in smaller chunks over > the same HTTP > connection and as part of one HTTP POST? > > /Pankaj. > > > -----Original Message----- > > From: Zhang, Li [mailto:[EMAIL PROTECTED]] > > Sent: Monday, February 04, 2002 4:24 PM > > To: '[EMAIL PROTECTED]' > > Subject: RE: High Volume > > > > > > I know there's no restriction on the size of the message in > > the SOAP spec, > > but if SOAP cannot handle "continuous stream" I won't use it > > to send a large > > data set. As you said most of current implementations are > > DOM-based, which > > just eat all your server memories. > > > > Li > > > > -----Original Message----- > > From: Mukund Balasubramanian [mailto:[EMAIL PROTECTED]] > > Sent: Monday, February 04, 2002 5:22 PM > > To: [EMAIL PROTECTED] > > Subject: Re: High Volume > > > > > > 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 > > > > > > > >
