The overall goals is to discourage users from overloading the Mqtt network with unnecessary messages. We'd like to cap those messages ideally before publishing. Any message we deny publishing for performance purposes we should warn the user of the reason. We also want to do be wary of the overhead cost of evaluating each message which may cost local performance. Can we:
- globally deny messages over 100ms average over 1 second per object id, or is it better to only warn if the threshold is crossed?
- globally deny messages with the same json payload, sans timestamp, since they are not providing any updates to the scene graph?
The overall goals is to discourage users from overloading the Mqtt network with unnecessary messages. We'd like to cap those messages ideally before publishing. Any message we deny publishing for performance purposes we should warn the user of the reason. We also want to do be wary of the overhead cost of evaluating each message which may cost local performance. Can we: