Difference between Fast Web Services and Fast Infoset


A question i often get asked is:

What is the difference between Fast Web Services and Fast Infoset?

It is easy to get confused between the two because of the way i first used the "Fast Web Service" term (in 2003) and then the adoption of the term for the standard in the ITU-T and ISO organisations. Here I will try and clearly explain the connections between them. When I refer to "Fast Web Services" and "Fast Infoset" it means I am refering to the standards.

Fast Web Services and Fast Infoset are complimentary.

Fast Infoset specifies how to encode an XML infoset in binary.

Fast Web Services specifies two ways of encoding SOAP messages in binary using Fast Infoset or a more optimized form.

The first part specifies how to encode SOAP message infosets using Fast Infoset. This is the part of Fast Web Services that has been implemented in JWSDP 1.6 and JWSDP 2.0.

The second more optimized, and complex, part of Fast Web Services specifies the use of WSDL, X.694, an ASN.1 schema for the SOAP message infoset, and the ASN.1 packed encoding rules. This can produce highly compact binary SOAP messages that are very efficient to serialize and parse.

The first, using Fast Infoset, is easier to integrate into an existing Web service stack that uses the JAX-RPC, JAX-WS and JAXB 1.x/2.0 APIs, where as the second is more complex. In addition the first does not depend on WSDL so can be considered more "loosely-coupled". So, for now, we have focused our open source development and product efforts on Fast Web Services using Fast Infoset.
Comments:

Post a Comment:
  • HTML Syntax: NOT allowed
About

sandoz

Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today