[DRMAA-WG] other IDL issues
andre at merzky.net
Wed Jun 22 07:19:01 CDT 2011
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
My $0.02, Andre.
Nothing is ever easy...
More information about the drmaa-wg