LeRoy,
One observation for the vendor. Using GZIP will decrease the
system's processing efficiency (throughput) in all cases except when
running on a low-bandwidth network in which the extra time needed for
compressing is offset by the time needed to transmit fewer bytes.
Using FI, OTOH, has the potential of increasing the processing
efficiency while at the same time reducing the bytes on the wire by
about half. Thus, FI will optimize both axes (space and time) while
GZIP may optimize only one (space).
Also note that JAX-WS incorporates an HTTP-based content
negotiation for FI, where a client initiates an exchange in XML but
includes 'application/fastinfoset' in the list of accepted content
types. This allows an FI-enabled server to reply in FI and continue
the conversation using this optimized encoding. In this sense, FI in
JAX-WS is a very non-disruptive technology.
-- Santiago
On Aug 24, 2006, at 7:34 AM, Paul Sandoz wrote:
> Hi,
>
> In addition to Fast Infoset (FI) with JAX-WS, Glassfish (as of b06)
> now has HTTP cpmpression support (i.e. GZIP transport encoding) [1].
>
> What platform is the other vendor using? Interoperation using FI
> will only occur if both sides are capable of processing FI.
>
> Depending on your efficiency requirements (serializing, parsing and
> size) and interoperability requirements FI, Compressed XML or
> Compressed FI may meet your needs.
>
> Paul.
>
> [1] http://weblogs.java.net/blog/jfarcand/archive/2006/06/
> enabling_http_c_1.html
>
> Sameer Tyagi wrote:
>> Can you elaborate a bit on what you want to do ?
>> JAX-WS has a built in implementation for the FI standard, you can
>> switch it on using
>> a system property. Perhaps that will work for you ?
>> See
>> http://java.sun.com/developer/technicalArticles/xml/fastinfoset/
>> http://java.sun.com/developer/technicalArticles/WebServices/soa2/
>> fastinfoset-soa.html
>> https://fi.dev.java.net/
>> http://blogs.sun.com/roller/page/sandoz?
>> entry=how_to_enable_fast_infoset
>> /s
>> LeRoy Hall wrote:
>>> I'm new to JAX-WS and am working on developing a client to
>>> consume a vendor's WSDL. This vendor is requiring that we
>>> compress our messages, however I can't seem to find any
>>> information about how to get JAX-WS to compress the message
>>> before sending it. Does anyone have any information about this?
>>> Thanks much.
>>>
>>> --------------------------------------------------------------------
>>> ----
>>> All-new Yahoo! Mail <http://us.rd.yahoo.com/evt=43256/*http://
>>> advision.webevents.yahoo.com/mailbeta>- Fire up a more powerful
>>> email and get things done faster.
>> --
>> ---------------------------------------------------------------------
>> ---------
>> Accessline: 1-877-325-9504 Internal: x51601
>> Timezone : EDT - Eastern Standard Time, GMT -5:00
>> AIM : sameersjc
>> Blog : blogs.sun.com/sameert
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_jax-ws.dev.java.net For
>> additional commands, e-mail: dev-help_at_jax-ws.dev.java.net
>
> --
> | ? + ? = To question
> ----------------\
> Paul Sandoz
> x38109
> +33-4-76188109
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_jax-ws.dev.java.net
> For additional commands, e-mail: dev-help_at_jax-ws.dev.java.net
>