Snappy capability types and attributes

Zygmunt Krynicki zygmunt.krynicki at
Tue Nov 17 16:39:47 UTC 2015

I'd like to thank everyone for participating. I will return to your
replies tomorrow as I'm about to EOD soon.

For now I'd like to stick to the hook because it is _easy_ and has a
benefit of moving us forward. I'd like to have useful demo of
capabilities doing more than we can do with hwassign today in a few
weeks. Hooks are the bare minimum needed to get us there. That doesn't
have to be the end of the road though so we can get back to the API
problem space again later.

Best regards

On Tue, Nov 17, 2015 at 5:29 PM, John Lenton <john.lenton at> wrote:
> On 17 November 2015 at 16:18, Ted Gould <ted at> wrote:
>> On Tue, 2015-11-17 at 13:10 -0200, Gustavo Niemeyer wrote:
>> > A REST API is just an API. How do we allow snaps to react to events?  Would
>> > we implement a server doing HTTP polling on every snap?
>> I imagine the same way REST handles events on the web, by requesting an
>> "infinite file" that updates with status. This will have to be done several
>> places in the Snappy REST interface as it'll be needed for things like
>> status of downloading snaps for a GUI progress bar
> so now instead of having a program that's called when and if an event
> happens, there is are two programs running all the time in case an
> event happens?
> --
> snappy-devel mailing list
> snappy-devel at
> Modify settings or unsubscribe at:

More information about the snappy-devel mailing list