Hi Andrew, Thanks for the reply
I agree the way API is designed, its asynchronous system. But its tough to decide on to estimate how long a machine might take to reach STOPPED state. Anyway other option would be check the node state again and send the confirmation. Please share your thoughts on this. Thanks & regards, Poornima.BS On Mon, Dec 19, 2016 at 8:06 PM, Andrew Phillips <aphill...@qrmedia.com> wrote: > How can i handle such situation in my application where i, >> >> 1. raise a request for stopping node and get back success response saying >> current state is stopping. >> 2. raise a request for starting node i get node not in a state from which >> it can be started >> > > In between 1 and 2, would it be possible for you to wait until the machine > is actually in state STOPPED (rather than STOPPING)? The success response > for 1 is intended, by the way: it indicates that your request to stop the > machine was successful. > > Like many asynchronous systems where operations may take a long time, that > does not mean that the request has actually *completed* - just that it has > been *received*/is being acted upon. > > Regards > > ap >
