Re: to be effcient or not to be efficient

Toby Hudon wrote:

> As for latency, what do you think the benefits would be of a message "timestamp before call" latency field? That is, when the application issues a message, the last line before the actual passing to the pipeline is a timestamp into a field in the data. Then when each object gets the data, it does the same thing into a seccond field (so the original timestamp of the call is preserved but the second one overwrites with each "update"), but only if it modifies the data. Thus each app can compare the existing field values and know its own latency on the system it's being run on. When the call is finally finished and the app gets it back, it knows what the latency of the pipeline was. We could use this information at the app or even component level to decide when to drop frames or change types of processing to remain realtime.

IMO designing a "smart" system is not a good thing. It will end up never 
working in most cases ;)