Listening for snappy events on snapd interface

Gustavo Niemeyer gustavo.niemeyer at
Wed Feb 3 15:35:17 UTC 2016

Hi Robert,

Yes, it makes sense, and we are even cooking a neat state tracking
mechanism that will make this much easier to code. I'll send out the spec
for public review in a moment.

This isn't in place yet, though, and we also don't have anything specified
for the API. So it may still take a little while before that's in place.

On Tue, Feb 2, 2016 at 9:22 PM, Robert Ancell <robert.ancell at>

> 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?
> --Robert
> --
> snappy-devel mailing list
> snappy-devel at
> Modify settings or unsubscribe at:

gustavo @
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the snappy-devel mailing list