Changes between Version 1 and Version 2 of MartinAsync

Show
Ignore:
Timestamp:
2008/02/14 11:42:19 (11 years ago)
Author:
matthew.pocock
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • MartinAsync

    v1 v2  
    1 = Martin Async use-cases = 
     1= Martin Async use-cases - SOAPLAB = 
    22 
     3SoapLab wraps business logic, described in ACD files. Often, the business logic is implemented as command-line applications. This includes those in Emboss. To support async access, SoapLab implements [http://www.omg.org/technology/documents/formal/lsae.htm lsae]. The implementation of this is documented at the [http://soaplab.sourceforge.net/soaplab2/API/index.html soaplab2 API], and in particular, the [http://soaplab.sourceforge.net/soaplab2/API/org/soaplab/share/Analysis.html Analysis] class. 
     4 
     5Asynchronous invocation is required by SoapLab as the underlying buisness logic may be long-running, and timeouts may occur in any layer of the transport between client and server. 
     6 
     7SoapLab is open-source (Apache license?). 
     8 
     9LSAE supports a full lifecycle for a job. 
     10 
     11 * jobID createJob(Map inputs) 
     12 * run(jobID) 
     13 * jobStatus getStatus(jobID) 
     14 * Map getResults(jobID) 
     15 * destroy(jobID) 
     16 
     17In the soaplab implementation, a SoaplabMap is used, which restricts the types of the map values to strings, numbers and binary data.