airavata-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Saminda Wijeratne <>
Subject Re: Enabling interactivity with executing workflow
Date Tue, 25 Jun 2013 20:15:11 GMT
Deciding upon the external parties is up to the gateway developer who plugs
Airavata to the gateway. Following an offline discussion with a gateway
developer led to following basic conclusions,

Interactivity for workflows can mean,

   - Interactivity between multiple workflows
   - Interactivity between the workflow and a user

There are 2 more variations to above scenarios

   - blocking interactivity (further execution of the workflow is halted
   until the interactive sessions has completed)
   - non-blocking interactivity

On Tue, Jun 25, 2013 at 4:14 PM, Saminda Wijeratne <>wrote:

> The next step in our workflow interpreter is to allow it to interact with
> external parties (eg: for controlling the execution pattern, providing
> additional data, canceling/redoing jobs etc). This will enable more
> fine-tuned control over how applications are executed and a different level
> of understanding of executing workflows.
> Your thoughts on this to drive the effort of improving workflow
> interpreter in Airavata is welcome.
> Thanks,
> Saminda

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message