The admin API has two commands that I'd really like to be consistent. > admin.vm.Start. This one waits until the VM is fully started.
> admin.vm.Shutdown This one returns immediately. This inconsistency is rather annoying and leaves me to connect to the event-feed to get a final "it shut down" information. I would like them both to wait until finished. I would argue that the inconsistency is a bug. Additionally, shutting down is certainly possible to fail (or, timeout), which would call for a 'kill'. I forsee having to write a lot more code to handle that case with the current API. Ideally "Shutdown" would not return immediately, but would return either on a) completion (success) b) timeout or failure (as an exception). So, my question is if this can still be made consistent, which would make my app using the API simpler. Second question; what is the general idea around backwards compatibility of the APIs? ps. I started documenting the API here; https://github.com/QubesController/qubes-api-cpp-lib/blob/master/Qubes.cpp#L29 -- Tom Zander Blog: https://zander.github.io Vlog: https://vimeo.com/channels/tomscryptochannel -- You received this message because you are subscribed to the Google Groups "qubes-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-devel/2203833.UaWprW4CiC%40mail. For more options, visit https://groups.google.com/d/optout.
