[DRMAA-WG] other IDL issues

[Andre Merzky]

Hi Daniel,


On Wed, Jun 22, 2011 at 12:37 PM, Daniel Gruber <dgruber at univa.com> wrote:
> Hi all,
>
> I've following findings:
>
> * MUTLITHREADING safety should be a capabilty since it is implementation specific. Also
>  source code portability requires it.

The spec leaves many things to the implementation - I don't think all
those degrees of freedom should be exposed for inspection, as
capabilities.  That will quickly grow and becom unwieldy.  For
example, optional fdeatures are: struct serialization, fetch info of
dead jobs, allow job annotations, support non-DRMAA jobs and
reservations, and many more.

Cabilities should only apply to API level features, IMHO, not to
implementation details.  Those need to go into the documentation of
the implementation.

My $0.02, Andre.



-- 
Nothing is ever easy...