Pablo Sabater [off-list ref] writes:
Rather than take these as function parameters, we take only the
transport object, and expect the caller to have placed the other two
into special fields in the transport struct. But this doesn't make much
sense. The set of oids and results are really only valid for one
request. There is no reason the transport would need to hang on to them
outside of the single function call.
Thanks for injecting some sanity into the mix.
With this fixed, are we happy with the entire series by now?
Thanks.