On Thu, 23 Mar 2017 17:36:32 +0000, Jenny Murphy wrote: > Hi, > I currently have a java application running in a snap. As part of some > added functionality my java application will need to communicate with a C > program executable. We are weighing up the options of how this would work. > The probably obvious way is to build a new snap which contains the C > program executable. Then we need some way of inter snap communication. > > So my first question is what is recommend for INTER snap communication, how > is it supposed to work?
Some form of stable IPC would provide the best robustness. There are alternatives using the content interface but that provides a level of coupling you might not want. Either of these might need an interface. > Alternatively could one snap contain two binaries? In this way could > traditional linux inter process communication methods be used? This is my > second question. Yes, there are many cases for this already. A good example is lxd, it bundles the lxc client and the lxd daemon. You can start this way and if your C application becomes a shared resource among many other snaps you can consider moving over to a two-snap model with some form of IPC and an interface. -- Sent using Dekko from my Ubuntu device -- Snapcraft mailing list Snapcraft@lists.snapcraft.io Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/snapcraft
