Changes between Version 5 and Version 6 of LargeData

Show
Ignore:
Timestamp:
2008/02/15 15:08:00 (10 years ago)
Author:
tmo
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • LargeData

    v5 v6  
    1 == Large SOAP Attachments == 
     1== Large data management in service APIs == 
    22 
    33One problem of webservices is sending large data chunks around - something you want to minimise. Not only for performance, but also because long transmissions may break. SOAP attachments are not ideal. One way to avoid sending data through SOAP is to send by reference, e.g. through the use of a URI ([http://hackathon.dbcls.jp/search?q=lsid&wiki=on&changeset=on&ticket=on LSID]) referral - which will delay fetching data until the last moment and may be optimised, e.g. through a bittorrent download (as discussed on [wiki:BioShare Bio.share/Bio.slurp]). 
     4 
     5We do not recommend passing large data through SOAP attachments in web services or as large SOAP body elements - any such approach is highly inefficient (Base64 encoding causes an expansion of binary data) and existing web service client stacks behave badly on large documents. In addition the advertisment of such mechanisms is poorly supported (there are standards to declare attachment input and output types but we've never seen anyone use them so in effect it is a hidden behaviour - as all behaviours of a good service should be exposed in the service metadata this is a bad thing). 
    46 
    57Biomoby has proposed a mechanism to allow parts of the moby data to be referenced to achieve this in their framework. The reference types can be advertised in the moby central metadata registry and therefore made available to clients such as Taverna.