Saturday, June 04, 2005
Interface vs. Message
Distributed component models like CORBA and J2EE mandate the usage of formal interfaces using IDL, Java etc. So the client and the server have to have the same interface file (from which you create your stubs and skeletons). This is how interoperability is achieved. Web Services on the other hand don't need you to define a formal interface that has to be shared between the client and the server. Interoperability is achieved by agreeing on the message that gets transferred between the client and the server. The way the message actually gets generated is not specified. This is analogous to the way business is done in everyday life - we have a shared understanding of the messages and documents we exchange. Focusing on the message vs. the interface decouples the programming model from the data that needs to be exchanged for the client and server to communicate with each other greatly simplifying interoperability.
Distributed component models like CORBA and J2EE mandate the usage of formal interfaces using IDL, Java etc. So the client and the server have to have the same interface file (from which you create your stubs and skeletons). This is how interoperability is achieved. Web Services on the other hand don't need you to define a formal interface that has to be shared between the client and the server. Interoperability is achieved by agreeing on the message that gets transferred between the client and the server. The way the message actually gets generated is not specified. This is analogous to the way business is done in everyday life - we have a shared understanding of the messages and documents we exchange. Focusing on the message vs. the interface decouples the programming model from the data that needs to be exchanged for the client and server to communicate with each other greatly simplifying interoperability.
Comments:
Post a Comment
