search for: opaque_ptr

..._on_update, and read size into an opaque ptr to struct 4) nbdkit calls my_plugin.pread passing in the usual args + the opaque ptr 5) my_plugin.pread makes an asynchronous read call with a handler set on completion to call nbdkit_reply_read(conn, opaque ptr, buf) or on error nbdkit_reply_error(conn, opaque_ptr, error) 6) my_plugin.pread returns back to nbdkit without error after it has started the async op but before it has completed 7) nbdkit doesn't send a response to the conn->sockout beause when the async op has completed my_plugin will callback to nbdkit for it to send the response 8) nbdkit...

...ue ptr We can't change the existing API, so this would have to be exposed through new plugin entry point(s). > 5) my_plugin.pread makes an asynchronous read call with a handler set on > completion to call nbdkit_reply_read(conn, opaque ptr, buf) or on error > nbdkit_reply_error(conn, opaque_ptr, error) > 6) my_plugin.pread returns back to nbdkit without error after it has > started the async op but before it has completed > 7) nbdkit doesn't send a response to the conn->sockout beause when the > async op has completed my_plugin will callback to nbdkit for it to send th...

...nge the existing API, so this would have to be exposed > through new plugin entry point(s). > > > 5) my_plugin.pread makes an asynchronous read call with a handler set on > > completion to call nbdkit_reply_read(conn, opaque ptr, buf) or on error > > nbdkit_reply_error(conn, opaque_ptr, error) > > 6) my_plugin.pread returns back to nbdkit without error after it has > > started the async op but before it has completed > > 7) nbdkit doesn't send a response to the conn->sockout beause when the > > async op has completed my_plugin will callback to nbdk...