Concept for signal update frequency

[erikbosch]

The concept for controlling how often signal value updates shall be sent to clients is not well defined and not well documented. We have some pieces here and there:

• In DBC Feeder there is a possibility to control how often signals are sent to Databroker
• Databroker has some built-in support for selecting ChangeType, but it is typically not controllable by either API or config

... and we lack an overall concept documentation giving recommendations for deployments ("How to keep clients happy while minimizing CPU usage and data transfer)

[SebastianSchildt]

Maybe related #560

[SebastianSchildt]

I think cleint side this is worked on here as well #734

anyway, as this is the "old" repo shall we close here @erikbosch ?

[erikbosch]

There are things going on here and there - see also eclipse-kuksa/kuksa-python-sdk#21.

What we possibly need to discuss is where to put/describe the concept from an end to end perspective, including also providers like can/dbc provider. The pull requests so far are very much based on code snippets, and doe not really give any good documentation/recommendations. But where should we put that? That is also true for some other documentation in https://github.com/eclipse/kuksa.val/tree/master/doc. Do we possibly aim to use kuksa-website for hosting general KUKSA documentation?

[erikbosch]

We are about to archive this repo soon. If you consider this issue as important please file a new issue at one of the new Kuksa repos at https://github.com/eclipse-kuksa