Skip to main content

MTOM / Fast Infoset Questions

4 replies [Last post]
phlogistic
Offline
Joined: 2004-01-15

Is Fast Infoset the same thing as MTOM (Message Transmission Optimization Mechanism)?

Is Microsoft's WSE (http://msdn.microsoft.com/webservices/webservices/building/wse/default.aspx)
compatible with Fast Infoset?

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
phlogistic
Offline
Joined: 2004-01-15

Right on about MTOM / Sun. Thanks for all your help.

Hope to read more about it on the weblogs.java.net!

phlogistic
Offline
Joined: 2004-01-15

Thanks Paul.

So JAX-WS 2.0 will be Sun's MTOM specification & RI (Glassfish).

It seems like there is a lot of support backing XOP & MTOM (W3C, Sun & Microsoft working together, Tango, etc.)

I don't get a jist of when any major web servers (i.e. Weblogic, JBoss, Websphere) will start supporting JAX-WS 2.0. Any ideas who is slated for what dates?

sandoz
Offline
Joined: 2003-06-20

Sun's JAX-WS 2.0 RI implementation supports the MTOM and Fast Infoset standards. And JAX-WS 2.0 Web services can be deployed on Glassfish.

Note that there is no such thing as Sun's MTOM specification or Sun's Fast Infoset specification. Both are standards, there is such a thing as Sun's implementation :-)

Also the JAX-WS RI 2.0.1 is going through a rearchitecture to efficiently support all those additional Web services related functionality, like addressing, reliable messaging and secure conversation. At this point Fast Infoset is currently not implemented in the rearchitectured implementation, but it will be soon!

I presume that since BEA, JBoss and IBM voted yes on the JAX-WS JSR [1] that they are planning to implement and/or support JAX-WS 2.0 on their application/web servers. I do not know exact details, so i would recommend asking that question on related forums.

[1] http://www.jcp.org/en/jsr/results?id=3748

sandoz
Offline
Joined: 2003-06-20

Fast Infoset is not the same thing as MTOM but it can solve the same problem i.e. not having to base64 encoding binary content.

Fast Infoset is a binary encoding of the XML information set, where as MTOM is a transformation of an infoset into another infoset where base64 'clobs' are instead represented as 'blobs', which are MIME attachments.

Fast Infoset is more efficient than MTOM at handling 'blobs' when the binary content is small and the overhead of the MIME part headers is large. Fast Infoset can encode 'blobs' for attribute values, and also support the binary encoding of integer and real numbers.

Microsoft's WSE does not support the Fast Infoset encoding. They have their own proprietary binary encoding of the XML infoset. But it is possible to plug in a Fast Infoset encoding into WCF, which is what project FIFI does.

Hope this helps,
Paul.