On Tue, Sep 10, 2019 at 07:58:49AM -0500, Eric Blake wrote:
> On 9/10/19 5:01 AM, Richard W.M. Jones wrote:
> > Of course at the moment nbdkit parses the NBD export name option but
> > doesn't really do anything with it (except logging it).
> >
> > I wonder if we should make this available to plug
On 9/10/19 5:01 AM, Richard W.M. Jones wrote:
> Of course at the moment nbdkit parses the NBD export name option but
> doesn't really do anything with it (except logging it).
>
> I wonder if we should make this available to plugins, in case they
> wish to serve different content to different clien
On Tue, Sep 10, 2019 at 11:01:10AM +0100, Richard W.M. Jones wrote:
> The implementation of this is straightforward. It simply reads the
> exportname global from the server and returns it. It also doesn't
> change the existing API at all.
Sorry - of course I don't mean returning the global expor
Of course at the moment nbdkit parses the NBD export name option but
doesn't really do anything with it (except logging it).
I wonder if we should make this available to plugins, in case they
wish to serve different content to different clients based on the
export name. Note I'm not suggesting th
