Comment 14 for bug 1384286

Ah, OK, it seems the penny is finally dropping :-)

So, if I understand you correctly, you are saying that @{HOME}/.local/share/unity-scopes/leaf-net/@{APP_PKGNAME}/* is the writable cache directory for the scope (exactly as it is now), and @{HOME}/.local/share/@{APP_PKGNAME}/* is the readable directory where the scope can read data produced by the app?

I think we can do this. In practice, this would mean adding an app_directory() method to the scopes API that returns the path to the readable directory that a scope can use to pick up data from the app. There are some doc implications, but it's doable.

I take it that the readable directory would not be applicable to scopes that do *not* install together with an app in the same click package? (We would throw an exception if a scope doesn't have an associated app and tries to get the directory name.)

Now, if I have this picture correct, it implies that a scope can read from an app, but an app cannot read from a scope. Is that what we want? If so, I think I'm good with this. (I haven't implemented anything yet, so there are the usual caveats. But, off-hand, I don't see a show-stopper.)