I have a plugin that needs to store a collection of arbitrarily large files in a persistent way. (Dozens of megabytes; we're not talking gigabytes here.) I need to access them by name quickly (no fair making a big blob out of all of them).
Right now, I'm storing these files in a directory in ~/Library. That works fine of course, but means that they're not tied to Indigo at all. If the user takes their Indigo installation elsewhere, my files don't come along; and I don't get the nice auto-backup-on-version-upgrade behavior either.
I could store those files as properties of my plugin, but I hesitate because I'm not sure shuffling megabytes of data through rpc links is what you had in mind there. Do you have any guidance on size and throughput limits for plugin (or device) properties?
Or alternatively, can you provide or identify a directory inside /L/AS/PA/Indigo X.Y where a plugin can store files for its use? (Indigo X.Y/Preferences/<pluginid>.support might work...) The idea being, of course, that this would be a supported thing and the files get copied during a version upgrade.
I suppose I could also store those files inside my own plugin bundle, but I'm rather treating that as read-only (as every good code bundle should be).
Cheers (and happy almost-new year!)
-- perry