Default non-action is INV_OBJ, with no way to provide no response. #2
Description
If an object post processor does not otherwise provide a response to a request, the the SDO SVR Protocol Processor will automatically generate an ERR_INV_OBJ (invalid object ID) response, and this response cannot be prevented.
This is a problem when operating in a mixed environment where another SDO server may be responsible for providing some objects. While this is NOT an ideal situation, because the two SDO servers will not be aware of each other, it should still be possible for them to coexist mostly peacefully.
I am considering to add an action that will cause a non-response to a request.
I am also considering changing the default behavior so that the application must explicitly request the ERR_INV_OBJ response, instead of it being automatic, and then a non-response action will not be necessary. (The {PRIVATE} attribute will need to be removed from TX_ERR_INV_OBJ action then.