Displaying 3 results from an estimated 3 matches for "nbdkit_plugin_close".
2020 Jul 30
3
Re: [PATCH nbdkit v2] PROPOSED: server: Implement list_exports.
...fter_fork and .unload to
open a distinct connection into the plugin independent of any filter
clients, and which returns by reference a next_ops/nxdata pair that the
filter can then use in place of waiting for a per-connection
next_ops/nxdata passed through .prepare/.can_write/.pread/etc.
void nbdkit_plugin_close (struct nbdkit_next_ops *next_ops,
void *nxdata);
which a filter later calls to close its own connection into the
underlying plugin. Any plugin that uses these new functions would
probably implement a .open that does NOT call next_open(nxdata), because
it instead reu...
2020 Jul 30
0
Re: [PATCH nbdkit v2] PROPOSED: server: Implement list_exports.
...pen a distinct connection into the plugin independent of any
> filter clients, and which returns by reference a next_ops/nxdata
> pair that the filter can then use in place of waiting for a
> per-connection next_ops/nxdata passed through
> .prepare/.can_write/.pread/etc.
>
> void nbdkit_plugin_close (struct nbdkit_next_ops *next_ops,
> void *nxdata);
>
> which a filter later calls to close its own connection into the
> underlying plugin. Any plugin that uses these new functions would
> probably implement a .open that does NOT call next_open(nxdata),
&...
2020 Jul 22
3
[PATCH nbdkit v2] PROPOSED: server: Implement list_exports.
Updated proposal, taking into account the default export. Instead of
adding a second call, I made a couple of changes to list_exports:
(1) If the plugin has a concept of a default export, it should add it
as the first element in the exports list.
(2) There is a new default_only flag which tells the plugin that the
client is trying to request the name of the default export, so the