My use of the term "encoding" was ambiguous. I was referring to the use of
the Content-Encoding header in HTTP. There is a sample with the latest
called "gzip", which shows how to send gzip encoding from the client in the
request, as well as how to gzip the response from the server. Both client
and server will automatically recognize the Content-Encoding header an unzip
the content.
The gist of preparing for the call on the client is
SOAPContext ctx = new SOAPContext();
ctx.setGzip(true);
Vector params = new Vector();
params.addElement(new Parameter("data", inFileData.getClass(),
inFileData, null));
Call call = new Call("urn:gzip-sample",
"test",
params,
null,
Constants.NS_URI_SOAP_ENC,
ctx);
In other words, you enable gzip through the SOAPContext, which you provide
to the Call ctor. That's all there is to it.
Scott Nichol
----- Original Message -----
From: "Wyn Easton" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, September 24, 2002 11:02 AM
Subject: Re: Sending Large XML Element
> Thanks for the info. Scott. That is what I thought the
> answer would be. It's always good to get conformation.
>
> To use the gzip encoding do I specify that as
> the encoding style rather than literal when sending my
> XML Element? Thanks.
>
>
> --- Scott Nichol <[EMAIL PROTECTED]> wrote:
> > Memory is really the only constraint. Besides the
> > RAM in the machine, you
> > should be conscious of the size of the heap set for
> > the JVM. It will not
> > simply use memory until the machine is exhausted.
> >
> > For such a large payload, you should consider
> > working with a nightly drop of
> > the code, rather than release 2.3.1, because
> > subsequent to 2.3.1, the
> > ability to use gzip encoding was added.
> >
> > Scott Nichol
> >
> > ----- Original Message -----
> > From: "Wyn Easton" <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> > Sent: Monday, September 23, 2002 4:58 PM
> > Subject: Sending Large XML Element
> >
> >
> > > Hello:
> > > I'm working on a project where we could potentaly
> > send
> > > XML Elements that contain 10,000 child elements.
> > > The total size could be 60-80MB. We are using SOAP
> > RPC
> > > to pass the root Element as a parameter. The text
> > > strings contained in the child elements are no
> > very
> > > large. There are just a lot of them.
> > > Are there restrictions, other than the memory of
> > the
> > > machine, that would prevent this from working?
> > >
> > > Thanks.
> > >
> > > __________________________________________________
> > > Do you Yahoo!?
> > > New DSL Internet Access from SBC & Yahoo!
> > > http://sbc.yahoo.com
> > >
> > > --
> > > To unsubscribe, e-mail:
> > <mailto:[EMAIL PROTECTED]>
> > > For additional commands, e-mail:
> > <mailto:[EMAIL PROTECTED]>
> > >
> > >
> >
> >
> > --
> > To unsubscribe, e-mail:
> > <mailto:[EMAIL PROTECTED]>
> > For additional commands, e-mail:
> > <mailto:[EMAIL PROTECTED]>
> >
>
>
> __________________________________________________
> Do you Yahoo!?
> New DSL Internet Access from SBC & Yahoo!
> http://sbc.yahoo.com
>
> --
> To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
>
>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
