I think it will be handy to allow to capture screenshots of the running VM. However, right now curie executes the VM synchronously — curie run .. blocks until you quit. Which is a good feature I think, but it disallows us to implement curie make-screenshot command - this command will run in a separate process.
I'm thinking of allowing curie to expose a (local unix?) socket, over which the request to make screenshot can be sent. Running curie process with a VM would receive such request and perform an action, taking screenshot storing it into file. Also, it may send back the reply, indicating that request has been processed.
What are the alternatives?
- to process something like SIGUSR1, but that is not scalable and flexible, e.g. if we wanted to allow processing more events, SIGUSR1 won't let us do that.
- web socket — too broad I think, everyone would then be able to make screenshots over the network
- any other ideas?
I think it will be handy to allow to capture screenshots of the running VM. However, right now curie executes the VM synchronously —
curie run ..blocks until you quit. Which is a good feature I think, but it disallows us to implementcurie make-screenshotcommand - this command will run in a separate process.I'm thinking of allowing curie to expose a (local unix?) socket, over which the request to make screenshot can be sent. Running curie process with a VM would receive such request and perform an action, taking screenshot storing it into file. Also, it may send back the reply, indicating that request has been processed.
What are the alternatives?