Snappy capability types and attributes

Ted Gould ted at
Tue Nov 17 20:08:06 UTC 2015

On Tue, 2015-11-17 at 16:29 +0000, John Lenton 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?
Was more thinking that if the application implemented a service that
service would adjust based on capabilities while they were added. I
wouldn't expect an additional service for just communicating with
Snappy. For command line utilities they could read their configuration
when run. The difference there is whether you read and parse a file or
whether you read and parse a request to Snappyd. I don't know the
numbers, but I imagine they're not significantly different in
Frankly, with some of the flash in these embedded boards an HTTP
request may be faster than a config file read ;-)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part
URL: <>

More information about the snappy-devel mailing list