SCOOP:
------

  really like the Session API and Logical Files API... would help a lot.

  Everything looks ok and should be extremely valuable to SCOOP.

  For SCOOP ver 2 our job submission interface was from 
  Gram-job-manager -> Condor Master -> Condor Pool.  
  Reason : Portal was limited to GRAM submissions only. 
  One of the main difficulties we faced was interpreting 
  of error codes. It was very confusing what the exact error 
  code meant since there were layers of RMs. 
  
  I wonder if SAGA can help resolve such complexities.  :)

  <<< 
    Comment Andre:
    --------------

    Yes and no - if a SAGA implementation reports errors badly (maybe because it
    does not get good error messages from the middleware), we cannot do much
    apart from saying "Uh, bad!".

    However, at least you will have one and only one consistent and reliable way
    of error reporting on application level.

    The submission chain will be completely hidden.  However, if your grid
    requires the chain, you still need to implement it _somewhere_, be it in a
    saga adaptor, or behind a gatekeeper...
  >>>