developer:rpc_encoded

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Last revision Both sides next revision
developer:rpc_encoded [2011/03/02 13:31]
irina
developer:rpc_encoded [2011/03/02 13:33]
irina
Line 1: Line 1:
 ====== SOAP WSDLs - RPC/Encoded ====== ====== SOAP WSDLs - RPC/Encoded ======
 +===== Example of the code =====
 <​code>​ <​code>​
 <​soap:​envelope>​ <​soap:​envelope>​
Line 14: Line 14:
 There are a number of things to notice about the WSDL and SOAP message for this RPC/encoded example: There are a number of things to notice about the WSDL and SOAP message for this RPC/encoded example:
  
-=== Strengths ===+===== Strengths ​=====
  
   - The WSDL is about as straightforward as it's possible for WSDL to be.   - The WSDL is about as straightforward as it's possible for WSDL to be.
   - The operation name appears in the message, so the receiver has an easy time dispatching this message to the implementation of the operation   - The operation name appears in the message, so the receiver has an easy time dispatching this message to the implementation of the operation
  
-=== Weaknesses ===+===== Weaknesses ​=====
  
   - The type encoding info (such as xsi:​type="​xsd:​int"​) is usually just overhead which degrades throughput performance.   - The type encoding info (such as xsi:​type="​xsd:​int"​) is usually just overhead which degrades throughput performance.
developer/rpc_encoded.txt ยท Last modified: 2011/03/02 13:35 by irina

Page Tools