You should be able to write "Handlers" for Axis that will process the messages (both client and server) on the way in/out. This would allow you to support gzip'd data transparently.
This is how Axis is designed, to be extensible. See the documentation for architecture details. Note that on the client, you configure the handlers in the 'client-config.wsdd' file, pretty much the same way you do in the server-config.wsdd file. Hope this helps point you in the right diirection. -- Tom Jordahl Macromedia Server Development -----Original Message----- From: Brian W. Young [mailto:[EMAIL PROTECTED]] Sent: Friday, December 20, 2002 8:56 AM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: gzip support Yaron, I believe you are correct- thank you for clarifying. I hope others understand now as this can be powerful stuff if you have large messages. I've put a J2EE CompressionFilter class in front of the axis web application. This is simply the CompressionFilter that ships with Tomcat as an example. I believe this will compress the data outbound from the server to the client w/o much difficulty. As you say, the client is another issue. I'm not sure I'll have enough control as a user of the Axis API on the client to have it unwrap as a GZipOutputStream. It looks like all the IO stuff is pretty wrapped up and hidden from the user. Somehow I need to make the client capable of this. Anybody have ideas? I'm new to Axis so c someone suggest a class I might hack this functionality in to? Thanks Yaron Zakai wrote: >Hi, > > It looks like gzip support should be defined: > > The generated XML is gzip-ed, and the transport sends it as gzip content. >The receiver is involved as well, so axis client should support this as >well. > > This means that even the apache connector is used on the server side, there >should be support for this on the client side. > >Thanks, Yaron. > >-----Original Message----- >From: Chris Schaefer [mailto:[EMAIL PROTECTED]] >Sent: Friday, December 20, 2002 8:43 AM >To: [EMAIL PROTECTED] >Subject: Re: gzip support > > >HTTP has the option of some sort of compression. (zip, gzip? ) >So in theory the entire SOAP message can be compressed during transit. In >thinking about it, it's possible that this might be more a function >of Tomcat ( assuming that's what's hosting your axis servlet ), than >of Axis. >Finally if you use the apache connector between apache and tomcat, you could >probably get apache to do this compression for you.... > > >At 1:30 PM +0900 12/20/02, Toshiyuki Kimura wrote: > > >>Hi Brian, >> >> Do you mean that you want to transfer a gzip file via AXIS >>by using SOAP? If I understood what you said properly, you've >>just to implement a SwA(SOAP Messages with Attachments). >> >> Here is the spec: <http://www.w3.org/TR/SOAP-attachments> >> >> In addition, you will meet the sample code of SwA at the >>"axis-1_1beta\samples\attachments" in your environment. >> >>Best Regards, >> >> Toshiyuki Kimura <[EMAIL PROTECTED]> >> R&D Headquarters >> NTT DATA Corporation >> >>-----Original Message----- >>From: Brian W. Young [mailto:[EMAIL PROTECTED]] >>Sent: Friday, December 20, 2002 5:21 AM >>To: [EMAIL PROTECTED] >>Subject: gzip support >> >>I believe someone posted this question a couple weeks ago with no reply. >> Perhaps I'll have better luck. >> >>Does Axis support gzip streams? This is very important to me, because I >>am sending a lot of data. With home-grown code, I've witnessed a 2 meg >>document get compressed to 56K for an incredible boost in performance. >> >>Please advise, and thank you. >>Brian >> >> > > > >
