The problem was that the receiving system would choke when the XML responses were too long, so gzip wouldn't have helped it. I'm not sure what system/app they were using as it was with an external service provider, but it sounds pretty broken regardless. Probably some kind of fixed buffer overrun, yuck!
-ed On 6/14/05, Dave Newton <[EMAIL PROTECTED]> wrote: > Ed Griebel wrote: > > >We had a problem with XML having too many carriage returns and > >whitespace for a downstream system. > > > Heck, XML has too much NON-whitespace, too ;) > > >To solve the problem I wrote a > >simple javax.servlet.Filter instance that would get the response and > >strip out extraneous stuff using String.replaceAll() on the output > >from a HttpServletResponseWrapper instance. Not the most efficient, > >but it was expedient and the XML output was relatively small, > >especially when compared with the app's HTML output. > > > > > Was the difference between the performance of the .replaceAll so much > better than a gzip filter? > > Dave > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
