Listening for snappy events on snapd interface

Sergio Schvezov sergio.schvezov at canonical.com
Wed Feb 3 15:13:26 UTC 2016


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512



El 02/02/16 a las 20:22, Robert Ancell escribió:
> Hi,
> 
> The snapd interface currently allows an application to poll for
> the state of the snaps on a system either by getting the list of
> installed snaps or polling for the result of an async operation
> (e.g. install / remove).
> 
> It would be desirable to be able to subscribe to an event stream on
> the snapd interface so you could track all changes without polling.
> This would make: - Code more efficient by removing the need to poll
> your own async operations - A snapd client able to know when a
> separate client has installed / removed / changed state of a snap.
> 
> For example if you do the folowing request to snapd: GET
> /2.0/events (snapd blocks) (a client installs
> hello-world.canonical) (snapd returns) 
> {"snaps":{"hello-world.canonical":{"status":"installed"}}
> 
> Does this feature make sense for snapd?

Not only does it make sense, it was in the spec at some point as well.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCgAGBQJWshkWAAoJEKg9r3dpxJwKdeMH/jY1CW1Wr0vXip2qJQe7LLkV
R8AjI7xef/QxrAoOnSJGFl+kdEKi5wPAyqzVAAzH1oGImNIGIKkFiAqVLq7uCjqC
V7zsJyQQOChkjKKtFCb0LE6ysbZrPZrXXmf+VxtONTWfY/Mpg7IstdbzsqEuDVg5
rgoMRcvJaKfy0wbtBmkZ8R+Yj88Bi8xNHotWXJpWEHbMxEaEIpGbZ4VNiQGJjB54
+nI+kD++oCObbqviQDWQdoWsq6YMczWCsd7HwKG5n6eREwQPVSiKApQPnAA7wNmp
XnwL7QvXe44zZTHMdy8NDcorZzMEBhwbB9BlIPmY0AvVQuTii2buytGYOPt3efk=
=Wf0m
-----END PGP SIGNATURE-----



More information about the snappy-devel mailing list