FYI, I detailed some of what this might look like here: https://forum.snapcraft.io/t/how-to-use-dbus-run-session-on-ubuntu-core/7077/2 (where we allow snaps to create abstract sockets at @snap.SNAP_NAME.**). This concept could be extended in a similar fashion as the dbus interface, where it might be called 'socket' with a declared name that requires a snap declaration to use the name (that interface I would think would support both abstract and named sockets).
FYI, I detailed some of what this might look like here: https:/ /forum. snapcraft. io/t/how- to-use- dbus-run- session- on-ubuntu- core/7077/ 2 (where we allow snaps to create abstract sockets at @snap.SNAP_ NAME.** ). This concept could be extended in a similar fashion as the dbus interface, where it might be called 'socket' with a declared name that requires a snap declaration to use the name (that interface I would think would support both abstract and named sockets).