search for: nutdrv_qx_preprocess_command

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I would like to propose an interface change/extension, in order to be able to clearly differ from a PRE_SEND and a POST_RECEIVE item_t->preprocess-ing calls. IMHO there is no option to differ from item->preprocess(..), called from [1] and called from [2], at the moment. My idea is to extend the item_t->preprocess(..) with an additional

...nt commands/setvars are already filled with user-provided data, and the same would be true for those queries that need to be preprocessed: you'd only have to call the CRC/whatever function before quitting the query-preprocess one). Here's a first try at it: https://github.com/zykh/nut/tree/nutdrv_qx_preprocess_command Am I that far from what you want to achieve?

...dy filled > with user-provided data, and the same would be true for those queries > that need to be preprocessed: you'd only have to call the CRC/whatever > function before quitting the query-preprocess one). > > Here's a first try at it: > https://github.com/zykh/nut/tree/nutdrv_qx_preprocess_command That would work for me too. I'm looking forward to the merge. [1] https://github.com/networkupstools/nut/blob/master/drivers/nutdrv_qx.h#L97-L101 [2] https://github.com/nickma82/nut/commit/ce330a3873fd0a9243a61258db243a6eee=327e65