Hey! By looking at mesos-go <https://github.com/mesos/mesos-go> I've found that in example that ACK is done before handler is being called (here <https://github.com/mesos/mesos-go/blob/master/api/v1/cmd/msh/msh.go#L185>). Couldn't find similar way to do it after handler. I guess it depends on the use case but what usually works better (if any)? In my understanding if ACK is before handler then it may end up in situation where handler for e.g. RUNNING and FAILED states interleave:
RUNNING -> ACK -> handler for RUNNING starts -> FINISHED -> ACK -> handler for FINISHED starts -> handler for FINISHED ends -> handler for RUNNING ends. When ACK is always after handler then handler for RUNNING state will end before handler for FINISHED even starts. Any problems with such approach? -- BR, Michał Łowicki
