search for: nbdkit_export_list_add

Hi Eric, Nir. $SUBJECT - it's complicated! Imagine a scenario where we have extended the file plugin so you can point it at a directory and it will use the client-supplied export name to select a file to serve. Also we have extended the tar filter so that you can map tar file components into export names. You may be able to see where this is going ... Now we point the file plugin at a

...ng to do two separate connections (one for the listing, the second specifying a specific export). I was wondering if we should instead have the core server handle memory, similar to how we handle .exports (that is, the server allocates a container, passes it to the plugin, and the plugin calls nbdkit_export_list_add("...") as many times as it wants, where the server now frees the list instead of throwing the burden on the plugin). Offhand, I'm thinking either approach could be made to work, so it becomes a decision on which is easier to maintain (both from the perspective of the core server...