Does anybody know whether the HTTP BC shares all of the same features that the Glassfish HTTP listener supports such as gzip compression? If so, where are those parameters specified for the HTTP BC? (Compression of the XML can of course make a tremendous bandwidth savings for the typical XML passed around via SOAP.)
compression - on
Specifies use of HTTP/1.1 GZIP compression to save server bandwidth. Allowed values are:
off Disables compression.
on Compresses data.
force Forces data compression in all cases.
positive integer Specifies the minimum amount of data required before the output is compressed.
If the content-length is not known, the output is compressed only if compression is set to on or force.
Specifies a comma-separated list of MIME types for which HTTP compression is used.
If there isn't a way to configure the HTTPBC, What would be the best way to enable a gzip compression of the XML for the HTTPBC or JBI framework in general?
My first approach might be to just have a Glassfish HTTP-Listener based WebService delegate to the HTTPBC or more directly to the JBI SE components if possible. Maybe a filter on the HTTPBC to gzip the payload? Are there any plans to refactor HTTPBC to use the Glassfish HTTP Listener code, it appears to have more capability and options?