Changes between Version 3 and Version 4 of DXInterface


Ignore:
Timestamp:
11/07/06 10:59:30 (13 years ago)
Author:
astephen
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • DXInterface

    v3 v4  
    1212 
    1313 1. The code has so far only been tested with python ZSI-enabled client/server. That has allowed some interesting data structures that might be hard to encode in other languages/SOAP libraries. 
    14  2. Even ZSI is quirky - sometimes you have to package array items within their own length-1 arrays in order to pass them via SOAP. 
    15  3. The old WSDL model was very simple, mainly concentrating on "getOptions()" and "selectOptions()" methods. These are no longer considered very useful so it is likely we'll move to the more explicit "getDatasetOptions()" etc etc. 
    16  4. The client application needs better error handling from the server so all return values should include an error flag and a string that contains the error. This is planned but not implemented yet. 
     14 1. Even ZSI is quirky - sometimes you have to package array items within their own length-1 arrays in order to pass them via SOAP. 
     15 1. The old WSDL model was very simple, mainly concentrating on "getOptions()" and "selectOptions()" methods. These are no longer considered very useful so it is likely we'll move to the more explicit "getDatasetOptions()" etc etc. 
     16 1. The client application needs better error handling from the server so all return values should include an error flag and a string that contains the error. This is planned but not implemented yet. 
    1717 
    1818Given its fluid nature that is all we'll say about the DX WSDL for now. More pertinent to NDG is what you can send to the DX client as HTTP keyword-value pairs.