Question: "Kuksa Custom Controller"

[odra]

Hello,

There have been some discussions in #124, about how to handle "third party" VSS data types that are not part of the Kuksa codebase.

I would like to ask what would be the community take on what I will call "custom Kuksa controller".

The idea is that for Kuksa to delegate custom types to "external controllers", so once some data type that is not recognizable by Kuksa's databroker is being used, it will delegate that message to the controller that is responsible for dealing with said data type(s).

This means that Kuksa would require a "controller registration" mechanism to allow a controller to register itself within the Kuksa "runtime", each controller needed to be responsible for one or more data types.

Any thoughts?

[SebastianSchildt]

Can you tell in more detail what you are trying to achieve?

Hi, I am not sure, KUKSA needs "controllers" for that, I think like with structs, if there were a way to build an "Any" datatype (GRPC as "any" or "struct" that might help with this ) into KUKSA, where it just knows who to transfer the bytes, it might solve a lot of these kind of problems.

Then KUKSA would not need to know any new embedded datatypes, just the endpoints (i.e. Apps/providers) would need to know how to deal with it as is.