Anonymous:
----------

We will not being using the SAGA API for our use case.  SAGA evolved into
somethign very different from what we originally found potentially useful for
our use case (three calls- authorize(), copy_file(), and run_job()).  We aren't
interested in POSIX-like file semantics, threads, or the complexity of the API.

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

    Hmm, I checked their use case.  It is not trivial (e.g.  includes data base
    access, steering and visualization, at least to some extent).

    Also, a 'three call auth' we have (actually, we have zero call minimum and 5
    call maximum).  run_job and copy_file we have as well, both need exactly 2
    calls in total:

    {
      saga::directory dir;
      dir.copy (src, target);

      saga::job_server server ();
      server.run_job ("remote.host.net", "/bin/myjob");
    }

    So, it might be that they percieve SAGA as too complex, and that should be
    kept in mind, but the criticism is at least not well formulated I think.
  >>>