Well, event types are supposed to be different depending on what we want.. I
just like the idea of using actions because corresponds to spirit of Mistral :)
Btw, zaqar can be easily supported in a form of action (again, to be consistent
with what we do in the system).
Renat Akhmerov
@ Mirantis
On Thu, Sep 18, 2014 at 4:25 AM, Renat Akhmerov
wrote:
> Ok, here is what I think...
>
> I totally support the first option for its easiness in terms of
> understanding how it all should work (no need to figure out if some
> additional objects must be deleted if a workflow has been removed etc.
>
Ok, here is what I think...
I totally support the first option for its easiness in terms of understanding
how it all should work (no need to figure out if some additional objects must
be deleted if a workflow has been removed etc. etc.). We actually have two BPS
[0] and [1] where the idea was s
Use case:
The client software fires the workflow execution and needs to be know when the
workflow is complete. There is no good pool strategy as workflow can take
arbitrary time from ms to days. Callback notification is needed.
Solution is a webhook
Option 1: pass callback URL as part of star
