Missing interface: content sharing in the other direction
Bug #1655125 reported by
Kyle Fazzari
This bug affects 8 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
snapd |
Confirmed
|
Wishlist
|
Unassigned |
Bug Description
The content interface currently solves use-cases like an SDK snap, where multiple consumers use the contents of the provider. However, it doesn't solve the use-cases of plugin systems, where multiple providers (e.g. plugins, add-ons) want to get into the execution context of a single consumer (the main process). This would be useful for anything that exposes a plugin/add-on system: gedit, geany, nextcloud, etc.
tags: | added: snapd-interface |
affects: | snappy → snapd |
Changed in snapd: | |
status: | Triaged → In Progress |
To post a comment you must log in.
I think the content interface does solve that. What is harder is to figure out who can connect to who. I think the assertion system should control this, then the content system can do the rest.