[DRMAA-WG] DRMAA2 Draft 6, next steps, no conf call
andre at merzky.net
Fri Jun 24 01:49:17 CDT 2011
2011/6/24 Mariusz Mamoński <mamonski at man.poznan.pl>:
> 2011/6/24 Andre Merzky <andre at merzky.net>:
>> FWIW, this will be very hard on the end user. For example, tool developers
>> which build tools upon DRMAA have no control over how the tools are used,
>> and how instances are synchronized. This will be particularly difficult as
>> sessions are supposed to be persistent, and thus are *supposed* to be used
>> (i.e. opened) in different application instances.
> this is still possible but sequentially not concurrently and i think
> it serves most of the use cases. I guess it typically would be the
> same application but different run. I think one of the idea of
> introducing the restartable session concept in DRMAA 2.0 was that in
> DRMAA 1.0 you had to (in theory) keep the application running as long
> as you had some job in the system.
Yes, I agree that this is the most interesting use case.
Nothing is ever easy...
More information about the drmaa-wg