Issues.00234 - lordmundi/wikidoctest GitHub Wiki
00234: request for dcomm QoS settings
Summary: request for dcomm QoS settings
Created: 2010–03–31 18:48
Status: Released
Category: Request
From: frankie
Version: 2.0
Released_In: 2.2
Description:
this is a request to get dcomm to integrate a quality-of-service type setting where the user can specify certain nodes which are more important, and therefore should be prioritized in the dcomm queue.
Comments
jeff: 2010–07–22 - The previous version of the comm plugin and comm api calls would always transmit a nodes data when it was added to the send que, even if nothing had been changed. An example of this could be a simulation that continually sets a joint angle every pass, even when that joint angle is not moving.
When feature noc/now (No Change / No Write) is activated, comm will check that a node has changed in some way before adding it to the que for transmission. In this version of comm (July 2010) this feature is defaulted to on. For backward compatibility this feature may be deactivated (although I don't see any purpose is wasting the bandwidth).
Available Tcl/Tk commands to support throttling are:
doug.plugin dcomm always_enqueue ‹1|yes|0|no› : activates or deactivates forced enqueueing of nodes, even if unchanged